Hi Bulia,

I think I've found the cause, if it really is the same bug we're talking about. Apparently it first occurred in rev. 18995. The crash occurs at line 784 of sh-shape.cpp (line number is only valid for rev. 18995):

     Geom::Point tang2 = curve_it2->unitTangentAt(0);

Johan, could you have a look? It's related to 2geom and its your commit. Obviously, I wouldn't have asked this if I knew how to fix it myself ;-)

Thanks,

Diederik

On 11/10/2008 06:05 PM, bulia byak wrote:

On 11/9/08, Diederik van Lierop <mail@...1689...> wrote:
  

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 :-(
    

For the last three months (!!!), on and off, I'm fighting with a crash
that fits this description precisely: windows only, no gdb only. For
me it crashes intermittently when I arrow-key a path with markers in
one of my files. It may or may not be connected with snapping and/or
markers; even this I couldn't figure out with certainty. I now have an
idea which may allow us to debug such crashes; if it works out I will
let you know.

For now, one piece of advice I can give you is this: in
inkscape_crash_handler, place abort() as the first line. This will
make a crash to exit immediately. Without it, with my crash at least,
screen updates continued while Inkscape displayed the "crash occurred"
window, which made printf debugging incredibly difficult. With this
change, there's no crash dialog, and it exits immediately as soon as
it crashes.