[Scribus] Debugging Scribus
Mon Mar 5 09:39:53 CET 2007
> Original HTML messages are attached
> ----- Original Message -----
> Subject: [Scribus] Debugging Scribus
> From: ols6000 at sbcglobal.net <ols6000 at sbcglobal.net>
> To: scribus at nashi.altmuehlnet.de
> Date: 05-03-2007 8:43
> At 12:23 PM 2/4/2007, Gustavo Homem wrote:
> > > 4) How would I do the build process using either the Suse rpm or the
> > > tar archive?
> > >
> >tar zxvf scribus-184.108.40.206.tar.bz2
> >cd scribus-220.127.116.11
> >(install the missing xxxx-devel packages if the script complains about
> >missing libs)
> >make install (as root)
> I have succeeded in doing this. Now I am trying to debug the crash I
> get on printing, print previewing, or exporting to PDF. This crash is
> due to std::bad_alloc being thrown from QString::grow, according to
> gdb. I have submitted a bug report on this (#5262).
> It seems the executable built by the above process doesn't include
> debugging information for Qt, and maybe not for the other libraries.
> I have now downloaded what I hope is correct to build 18.104.22.168 on my
> system (IA32, Fedora Core 6):
> scribus-22.214.171.124-36.1.i386.rpm Installed successfully using
> package installer
> scribus-devel-126.96.36.199-36.1.i386.rpm Missing dependency freetype2-devel
> scribus-188.8.131.52-36.1.src.rpm Can't install; package installer
> "Cannot install source packages"
> scribus-debug-184.108.40.206-36.1.i386.rpm Installed successfully using
> package installer
> So here are my questions:
> 1) How do I install the src.rpm in such a way that Scribus can be built?
> 2) What is in scribus-devel and scribus-debug?
> 3) How do I do the build so as to include debugging information for
> all libraries?
> 4) Where do I find the freetype2-devel package? rpmfind shows a
> package "FreeType development libraries and header files, Fedora Core
> 6 updates for i386,
> that looks like the right thing, but attempting to download it gets
> an ftp error 550, "Failed to change directory".
> 5) Are there plans to change from Qt 3 to Qt 4?
> Any other tips on debugging will be welcomed.
Personally, I think you are complicating life a lot in doing it this way. If
you are going to be looking at the source code and attempting to debug
something, why not just grab the current source from 1.3.3.x cvs and build
with that. This is all outlined on docs.scribus.net under the installing
section. Given you have Scribus installed and running, you will have all of
the packages, apart from perhaps some of the devel packages for the
We are changing to Qt4 in 1.3.5. This will be the primary target of 1.3.5,
no new features. (also, dumping autotools, using cairo as the primary
renderer and moving to subversion)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the scribus