Crash when copying path with Attach Path LPE

[Terrene]

If a path has the Attach Path LPE, and is attached to another path, attempting to copy (ctrl-c) the path causes Inkscape to crash. The path can be cloned and duplicated from the Edit menu and by hotkey, but not copied.

In the attached file, copy the vertical line to reproduce the problem.

Inkscape version: 0.92.2 (5c3e80d, 2017-08-06)
OS: Windows 10

[Alvin Penner (apenner)]

- confirmed on Windows 10, Inkscape 0.92.2 (6c06d47, 2018-02-06)
- confirmed on Windows 10, Inkscape 0.92+devel (9d6b0e8, 2018-02-18)

no error messages were received in DOS, just a crash

[Alvin Penner (apenner)]

attached is the backtrace from Inkscape 0.92.2 (6c06d47, 2018-02-06)

Program received signal SIGSEGV, Segmentation fault.
0x037eb1ac in libinkscape_base!_ZNK8SPObject21nearestCommonAncestorEPKS_ () from c:\app\temp\inkscape_0.92.x\libinkscape_base.dll
(gdb) bt
#0 0x037eb1ac in libinkscape_base!_ZNK8SPObject21nearestCommonAncestorEPKS_ ()
   from c:\app\temp\inkscape_0.92.x\libinkscape_base.dll
#1 0x037cd92a in libinkscape_base!_ZNK6SPItem20getRelativeTransformEPK8SPObject ()
   from c:\app\temp\inkscape_0.92.x\libinkscape_base.dll
#2 0x0066f1c8 in ?? ()
Backtrace stopped: Not enough registers or memory available to unwind further
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x037eb1ac in libinkscape_base!_ZNK8SPObject21nearestCommonAncestorEPKS_ () from c:\app\temp\inkscape_0.92.x\libinkscape_base.dll
(gdb) c
Continuing.
[Inferior 1 (process 9264) exited with code 030000000005]

[Jonathan Hofinger (jhofinger)]

Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here.

Please feel free to file new bugs about the issues you're seeing at
http://inkscape.org/report.

Moved to: https://gitlab.com/inkscape/inbox/issues/1467
Closed by: https://gitlab.com/jhofinger