Such behavior often indicates the use of uninitialized memory or other memory access related bugs. I would recommend performing the tests under valgrind if possible.
Cheers, Marcus
Maximilian Albert wrote:
Hi,
Johan, many thanks for trying to fix this! I haven't tried your patch yet (and don't know if I'll get around to doing it soon), but I have a question regarding this:
If I do undo, redo, undo, while in gdb, I can go on indefinitely. It only bugs outside gdb.
Why is it that some bugs only show up when starting Inkscape from outside gdb? This has driven me mad a couple of times, too. Does anyone have an idea what's different and perhaps even how to avoid this discrepancy in behaviour?
Max
Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel