~suv just found a way to trigger the same crash directly in Inkscape when manipulating a path in the XML editor:
> Additional hints to reproduce the crash: draw a new compound path
> (with two sub-paths), and make sure that the second sub-path path
> (verify order in node tool by stepping through nodes with <TAB>) has
> more than two nodes (it does not appear to make a difference whether
> the nodes have extracted node handles or not). Insert the consecutive
> 'Z' (or 'z') commands in the XML editor before the 'M' (or 'm')
> command defining the second sub-path.
Crashes with the following error in Inkscape r14651 trunk build on Windows 7:
(inkscape.exe:3844): glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: lib2geom exception: Non-contiguous path (src/2geom/path.cpp:1043)
So it seems this issue could also emerge in other scenarios.
~suv just found a way to trigger the same crash directly in Inkscape when manipulating a path in the XML editor:
> Additional hints to reproduce the crash: draw a new compound path
> (with two sub-paths), and make sure that the second sub-path path
> (verify order in node tool by stepping through nodes with <TAB>) has
> more than two nodes (it does not appear to make a difference whether
> the nodes have extracted node handles or not). Insert the consecutive
> 'Z' (or 'z') commands in the XML editor before the 'M' (or 'm')
> command defining the second sub-path.
Crashes with the following error in Inkscape r14651 trunk build on Windows 7: exe:3844) : glibmm-ERROR **: path.cpp: 1043)
(inkscape.
unhandled exception (type std::exception) in signal handler:
what: lib2geom exception: Non-contiguous path (src/2geom/
So it seems this issue could also emerge in other scenarios.