crash when adding a node to a combined path (SIGSEGV in sp_nodepath_line_add_node())

[Eveha]

Inkscape version: 0.47 r22583 (built Feb 9 2010) - Fedora 12 (Constantine)

Steps to reproduce:

1 - create two paths
2 - combined them
3 - truncate combined path
4 - try to add a node on residual path

The last step produce a bug.

A test file is attached (combined paths are red colored)

[su_v (suv-lp)]

> 3 - truncate combined path

Can you explain how you 'truncate' a combined path? (Maybe a translation issue, I don't know which command you used here).

[Eveha (bugtracking)]

The tool used to truncate is "delete selected nodes" from node editor. The upper red line was before continuing to the right. This section is already deleted in demo file.

[su_v (suv-lp)]

Not reproduced with Inkscape 0.47 and 0.48+devel r9870 on OS X 10.5.8

But honestly I am not sure whether my steps correspond with your instructions to reproduce:

- insert node with mouse
The last segment on each sub-path (within the blue circle, where they nearly touch each other) is not selectable or draggable with the mouse (bug #290870), so inserting a node by double-clicking or Alt+Ctrl+clicking the path outline doesn't work (bug #662762). No crash when inserting nodes in other segments with the mouse.

- insert node with the keyboard or tool controls
Inserting a node by selecting two adjacent nodes and using 'Insert node' on the controls bar doesn't crash Inkscape when done for the ending segments nor in other random segments on either sub-path.

Can you launch Inkscape from the command line, and paste the console messages when it crashes here?

[Eveha (bugtracking)]

in this new attachment (same as above but with a reduced circle), if i try to add a node on red line (inside the circle), inkscape crashes.
By launching inkscape from the command line i can see this message:
Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.

[su_v (suv-lp)]

Not reproduced: the segment can't be selected with the mouse nor clicked on (bug #290870 resp. bug #662762). When shift-clicking the segment's end nodes to highlight it and use the keyboard/tool controls, neither 0.47 nor 0.48+devel crash for me.

Possibly platform-dependent (like some internal 2geom function throwing an exception)? Do you happen to know how to create a backtrace with gdb [1]?

[1] <http://wiki.inkscape.org/wiki/index.php/Debugging_Inkscape#Debugging_Tips_for_Linux>

[su_v (suv-lp)]

@JazzyNico - can you test on Linux (and possibly Windows, too ;) )?

[Eveha (bugtracking)]

I've followed your advice and produced a gdb backtrace log file. This is the result in attachment.

[su_v (suv-lp)]

Thanks for the log, the backtrace is missing though: when the Segmentation fault occurs, type 'bt' at the gdb prompt to get a list of function calls (allows to examine the sequence of calls that leads to the current breakpoint).

[su_v (suv-lp)]

Any chance you can test with the current stable version Inkscape 0.48 or with a recent build of 0.48+devel (inkscape trunk)?

The code where the crash occurs (in 'src/nodepath.cpp') no longer exists in 0.48 and in the current development branch: The node tool was complete rewritten for 0.48 and the file removed in revision 8976. It is likely that the new code no longer crashes in this special situation, but this still needs to be verified.

[jazzynico (jazzynico)]

Reproduced on Ubuntu 10.04 and Windows XP, Inkscape 0.47 (after adding a node to the path inside the circle), but fixed in 0.48. My backtrace doesn't show the cause of the crash (no symbol installed for this version).

Anyway, the new node tool probably fixed this bug, and the report can be closed. Don't hesitate to reopen it if you run into this issue again with a more recent Inkscape version.

[Eveha (bugtracking)]

Ok, so after testing in 0.48 (Fedora 14) it seems that the bug has disappeared! That's fine