Segmentation fault (core dumped) when editing a spline

banenrok_glad_tot_eerste_heupwijdte_bug.sm2d (6.0 KB) I have a segmentation fault that happens consistently with this file. I’m trying to edit the spline that runs from SplPath_d_J2, wanting to mirror it to SplPath_d_2_J2_2.

Here’s the steps that lead to the crash:

  1. Open the properties of SplPath_d_J2
  2. Select path d
  3. Enter “Line_d_g1/8” in the Length field of the Second control point.

This crashes Seamly2d every time.

Here’s my Seamly2d version info again:

Seamly2D version: Seamly2D 0.6.0.1
Build revision: unknown
Build date: Built on Wed Sep 2 2026 at 20:17:56
Qt Version: 6.11.2
CPU: x86_64
Compiler: GCC 16.2.1 20260810 64 bit
CPU: x86_64
OS: Linux
OS Version: unknown
Locale: en_US
Country: United States
Language: English
Script Name: Latin
Decimal Point: ,
Negative Sign: -
Positive Sign: +
Direction: Automatic
System Codec: UTF-8
Arguments: seamly2d

We need the measurement file to to open the pattern.

Oops, of course! This is still a bit new to me :sweat_smile:

Danckaerts_model.smis (11.9 KB)

I was able to progress a bit further, somehow, but then it crashed when I tried to put (Angle1Spl_d_d_2 - 90) in the Angle field of path d :grimacing:

I have no issue with the Windows build. ???

I can check the appimage build later later.

BTW… the angle needs to be fixed.

That said though… I’m not sure why your decimal point appears to be a comma?

image

Check your prefs and see what the separator is set at… for en_US it should be a period… setting the separtor to default forces the app to use the “c” locale using the period.

Hmm, I was afraid of that. Well, no idea then… Yes, I was trying to fix the angle, but it kept crashing :sweat_smile:

In the Netherlands, we use a comma instead of a period, so this is expected behaviour!

Understood… I just saw that your locale is

image

Which does not use the comma thus my confusion.

Do you have any issues with other tools or just the Interactive - Spline?

Yeah, I noticed that too… But the behaviour is how I want it so I haven’t really looked into it.

I’ve had the occasional crash, but none as recurring as this one. I’ll see if I can get some logs for you. Does Seamly2d have a debug command line option?

Not that I’m aware of for the ‘release’ builds.

If you open Seamly from the terminal command line whatever logging it does will be visible in the terminal.

:unicorn:

I checked… the qDebug() statements will appear in a 'releae" build. Most of the qDebug() statements are used to track program flow rather than reporting specific errors. For ex:

void VDrawTool::SaveOption(QSharedPointer<VGObject> &obj)
{
    qCDebug(vTool, "Saving tool options");

coredump.txt (196.4 KB)

I did manage to get a coredump with a little bit more information! Now it happened when I right-clicked that spline.

I also tried running the program with gdb:

gdb_output.txt (28.5 KB)

Maybe this has some useful information?