-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of JonY Sent: vrijdag 6 juni 2008 11:35 To: Inkscape List Devel Subject: Re: [Inkscape-devel] How to create a FullDBG version in Win32 ?

Yann Papouin wrote:

...

Hi everyone,

I'm trying to create a fulldbg version (where the size of

the inkscape

...

symbol is > 200Mo) of inkscape but I don't know where to set the correct param Actually I'm using this wiki page : http://wiki.inkscape.org/wiki/index.php/Win32Port to build inkscape.

My objective is to create a bug report of an inkscape crash when previewing *.ico file -- Yann PAPOUIN,

Hi, Look for the file "build.xml", at the line which has:

<cc cc="${arch}gcc" cxx="${arch}g++"

change it to

<cc cc="${arch}gcc -g" cxx="${arch}g++ -g"

== alternatively == Look at the flags section under "Target: Compile", about line 278 for r18810, add a "-g" there.

The debug symbols file will still be "inkview.dbg" but about 200MB.

Hope I didn't start a flaming debate about abusing build.xml.

It is also possible to just build inkscape without "-g", and try to get a backtrace using the resulting inkscape.dbg. I will not list exact line numbers etc, but it will list functionnames which is usually all we need. I never build with "-g" (I remember it takes *a lot* longer that way), and get nice backtraces for myself.

Thanks for taking the effort of getting as detailed as possible backtraces!

Cheers, Johan

JonY wrote:

Look at the flags section under "Target: Compile", about line 278 for r18810, add a "-g" there.

Yes, this is where it goes. :-)

I only make a complete build with -g for everything every few weeks or so, because it is so large and slow to compile and link. In fact, the virtual server I use for autobuilds has an artificial memory limit on it which prevents it being able to link a full debug build. So I make them manually.

But if you know in which file(s) the problem lies, try this trick:

1: Do a normal build without -g 2: Determine which sources have the problem and delete the corresponding .o file in ${build}\obj. For instance, if the problem were in src\inkscape.cpp, delete build\obj\inkscape.o. If in src\trace\trace.cpp, delete build\obj\trace\trace.o. 3: Turn on -g and run buildtool again.

This way you get all of the debugging symbols that you need, but you don't make the entire program large.

bob

I reported it here: https://bugs.launchpad.net/inkscape/+bug/239152

2008/6/11 Alvin Penner <penner@...1856...>:

Yann Papouin-3 wrote:

...

my objective is to create a bug report of an inkscape crash when previewing *.ico file

if I disable the preview option, then I get the more detailed crash message :

C:\Python25\APP>inkcl.py GdkPixbuf loader failed

(inkscape.exe:1440): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion ` priv->closed == FALSE' failed

-- View this message in context: http://www.nabble.com/How-to-create-a-FullDBG-version-in-Win32---tp17686260p... Sent from the Inkscape - Dev mailing list archive at Nabble.com.

---

Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel