On Wed, 27 Oct 2004, Gustav Broberg wrote:
I've experienced exactly the same thing. I tried everything, removing the ~/.inkscape-dir, make distclean, --disable-mmx, changing boehm, gtk and gtkmm version, nothing solved it.
Then I changed gcc version to 3.3.4 (i compiled with 3.4.2 before), and that did it for me. (i'm on slackware, but that's probably not the issue).
Aha! It was starting to feel like a build issue. On my gentoo system I'm using version 3.3.3.
I did try this... and from what I can remember, the result was very different from time to time. My debugging skills are pretty weak, so i didn't manage to draw any conclusion from the result. I'll compile it with 3.4.2 again, and post the gdb-results here, or create a new bug in the tracker...
Hmm, almost sounds like at some point the execution is jumping to a random location in the code. That's often a symptom of referencing an undefined pointer or of having a bad address in there.
Since gcc 3.4.2 is pretty bleeding edge, it's possible there's a bug in it. Can you try 3.4.1 or 3.4.0 and see if the bug occurs with those versions too? It may also be valuable to read through the gcc bug list and/or post-3.4.2 changelog to see if others encountered similar problems.
Bryce