gimp @2.10.36 segfaults

[MaurizioLoreti]

Executing GIMP, I get a segmentation fault. I am running Sonoma 14.3.1 on a Mac Studio M2 Max. The bug report follows:

<!-- Copy-paste this whole debug data to report to developers -->

GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for macos
# C compiler #
	Apple clang version 15.0.0 (clang-1500.1.0.2.5)
	Target: arm64-apple-darwin23.3.0
	Thread model: posix
	InstalledDir: /Library/Developer/CommandLineTools/usr/bin

# Libraries #
using babl version 0.1.106 (compiled against version 0.1.106)
using GEGL version 0.4.46 (compiled against version 0.4.46)
using GLib version 2.78.4 (compiled against version 2.78.4)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.14 (compiled against version 1.50.14)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.17.6 (compiled against version 1.17.6)

> fatal error: Segmentation fault: 11

Stack trace:

# Stack traces obtained from PID 23604 - Thread 0xa86ac #

(lldb) process attach --pid 23604

[MaurizioLoreti]

Any hint? Do you need more info? Please...

[MaurizioLoreti]

PLEASE...

[MaurizioLoreti]

<!-- Copy-paste this whole debug data to report to developers -->


```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for macos
# C compiler #
	Apple clang version 15.0.0 (clang-1500.1.0.2.5)
	Target: arm64-apple-darwin23.3.0
	Thread model: posix
	InstalledDir: /Library/Developer/CommandLineTools/usr/bin

# Libraries #
using babl version 0.1.106 (compiled against version 0.1.106)
using GEGL version 0.4.46 (compiled against version 0.4.46)
using GLib version 2.78.4 (compiled against version 2.78.4)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.14 (compiled against version 1.50.14)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.17.6 (compiled against version 1.17.6)

```
> fatal error: Segmentation fault: 11

Stack trace:
```

# Stack traces obtained from PID 9859 - Thread 0x16106 #

(lldb) process attach --pid 9859

```

[kencu (Ken)]

there is nothing in your copy-paste that would give any clue.

Is there any more to it? Like the stack trace?

I installed gimp +quartz on my Sonoma M1 and it runs OK.

[kencu (Ken)]

anyway, MacPorts is not really the place to report segfaults running gimp. You would more profitably take that report to the gimp developers.

​https://www.gimp.org/bugs/report.html

[MaurizioLoreti]

Replying to kencu:

anyway, MacPorts is not really the place to report segfaults running gimp. You would more profitably take that report to the gimp developers.

​https://www.gimp.org/bugs/report.html

Sure? In the window that appears, with title "GIMP Crash Debug", I read these heading lines:

GIMP crashed with a fatal error: fatal error: Segmentation fault: 11

To help us improve GIMP, you can report the bug with these simple steps:
 • Copy the bug information to the clipboard by clicking:  "Copy Bug Information"
 • Open our bug tracker in the browser by clicking:  "Open Bug Tracker"
 • Create a login if you don't have one yet.
 • Paste the clipboard text in a new bug report.
 • Add relevant information in English in the bug report explaining what you were doing when this error occurred.

In the Console app, section "Crash reports", I don't see any entry related to GIMP. How can I get the stack trace, please? I tried again today, and on my Mac Studio M2 Pro running Sonoma 14.4 I still get the segmentation fault. gimp has been upgraded yesterday by MacPorts. Luckily, gimp 2.99.18 downloaded from the gimp site runs OK.

[kencu (Ken)]

My copy of gimp +quartz continues to work well on my M1 Mac.

If I were a gimp developer, and with this amount of information, the next thing I might ask you to do would be to launch gimp using lldb like this:

lldb gimp

then after the initial flurry of activity have you type:

run

and then, presuming it crashes again with "fatal error: Segmentation fault: 11", I would have you type:

bt

to get the stack trace, and then copy that information and paste it into the bug report.

[MaurizioLoreti]

Replying to kencu:

My copy of gimp +quartz continues to work well on my M1 Mac.

If I were a gimp developer, and with this amount of information, the next thing I might ask you to do would be to launch gimp using lldb like this:

lldb gimp

then after the initial flurry of activity have you type:

run

and then, presuming it crashes again with "fatal error: Segmentation fault: 11", I would have you type:

bt

to get the stack trace, and then copy that information and paste it into the bug report.

Thank you.