Hi,
-----Original Message----- From: Diederik van Lierop [mailto:mail@...1689...] Sent: 10 November, 2008 04:20 To: inkscape-devel Subject: [Inkscape-devel] Difficulties in backtracing a crash on XP
Hi,
Bug 292077 is giving me quite some difficulties in pin-pointing it. It crashes Inkscape, but I can only reproduce it on Windows (not on Linux), and only when I'm _not_ running gdb. To make things worse it even requires quite some patience to reproduce it. How does one find the cause of such a bug? I've tried attaching gdb after the crash (is that possible at all?), and sprinkled around lot's of std::couts, but I didn't get any closer. I could use some pointers here :-(
Apparently it only crashes when snapping is enabled, but it looks like it's not the snapping code itself that's crashing. The bug report is here:
https://bugs.launchpad.net/inkscape/+bug/292077
I have just reported to the bug tracking that:
I have not been able to reproduce the error, and I don't have problems moving snapping nodes in other files.
On XPSP3 single core.
Can it be a multiprocessor problem?
Preben
It's been around at least since v0.46, according to this report.
Thanks,
Diederik
PS: If you want to have a try at reproducing it yourself, then please use revision 20049 or older. Newer revisions snap less often and are therefore more difficult to break.
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel