GIM fatal error crash on opening
GIMP version: 2.10
Operating System: Mac OSX 10.9
Package: Installer from gimp.org
Description of the bug: Crashes after opening
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Configured with: --prefix=/Applications/Xcode-10.app/Contents/Developer/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.9.sdk/usr/include/c++/4.2.1
Apple LLVM version 10.0.0 (clang-1000.11.45.2)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: /Applications/Xcode-10.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
using GEGL version 0.4.12 (compiled against version 0.4.12)
using GLib version 2.58.1 (compiled against version 2.58.1)
using GdkPixbuf version 2.36.12 (compiled against version 2.36.12)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.4 (compiled against version 1.42.4)
using Fontconfig version 2.13.0 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)
fatal error: Segmentation fault: 11
Stack trace:
# Stack traces obtained from PID 891 - Thread 19712 #
Usage:
lldb -h
lldb -v [[--] <PROGRAM-ARG-1> [<PROGRAM_ARG-2> ...]]
lldb [-a <arch>] -f <filename> [-c <filename>] [-s <filename>] [-o <none>] [-S <filename>] [-O <none>] [-Q] [-e] [-x] [-X] [-l <script-language>] [-d] [[--] <PROGRAM-ARG-1> [<PROGRAM_ARG-2> ...]]
lldb -n <process-name> [-w] [-s <filename>] [-o <none>] [-S <filename>] [-O <none>] [-Q] [-e] [-x] [-X] [-l <script-language>] [-d]
lldb -p <pid> [-s <filename>] [-o <none>] [-S <filename>] [-O <none>] [-Q] [-e] [-x] [-X] [-l <script-language>] [-d]
lldb -P
lldb [-a <arch>] -r [<none>]
-h
--help
Prints out the usage information for the LLDB debugger.
-v
--version
Prints out the current version number of the LLDB debugger.
-a <arch>
--arch <arch>
Tells the debugger to use the specified architecture when starting
and running the program. <architecture> must be one of the
architectures for which the program was compiled.
-f <filename>
--file <filename>
Tells the debugger to use the file <filename> as the program to be
debugged.
-c <filename>
--core <filename>
Tells the debugger to use the fullpath to <path> as the core file.
-p <pid>
--attach-pid <pid>
Tells the debugger to attach to a process with the given pid.
-n <process-name>
--attach-name <process-name>
Tells the debugger to attach to a process with the given name.
-w
--wait-for
Tells the debugger to wait for a process with the given pid or name
to launch before attaching.
-s <filename>
--source <filename>
Tells the debugger to read in and execute the lldb commands in the
given file, after any file provided on the command line has been
loaded.
-o
--one-line
Tells the debugger to execute this one-line lldb command after any
file provided on the command line has been loaded.
-S <filename>
--source-before-file <filename>
Tells the debugger to read in and execute the lldb commands in the
given file, before any file provided on the command line has been
loaded.
-O
--one-line-before-file
Tells the debugger to execute this one-line lldb command before any
file provided on the command line has been loaded.
-Q
--source-quietly
Tells the debugger suppress output from commands provided in the
-s, -S, -O and -o commands.
-e
--editor
Tells the debugger to open source files using the host's "external
editor" mechanism.
-x
--no-lldbinit
Do not automatically parse any '.lldbinit' files.
-X
--no-use-colors
Do not use colors.
-P
--python-path
Prints out the path to the lldb.py file for this version of lldb.
-l <script-language>
--script-language <script-language>
Tells the debugger to use the specified scripting language for
user-defined scripts, rather than the default. Valid scripting
languages that can be specified include Python, Perl, Ruby and Tcl.
Currently only the Python extensions have been implemented.
-d
--debug
Tells the debugger to print out extra information for debugging
itself.
-r
--repl
Runs lldb in REPL mode with a stub process.
Notes:
Multiple "-s" and "-o" options can be provided. They will be processed from left to right in order,
with the source files and commands interleaved. The same is true of the "-S" and "-O" options.
The before file and after file sets can intermixed freely, the command parser will sort them out.
The order of the file specifiers ("-c", "-f", etc.) is not significant in this regard.
If you don't provide -f then the first argument will be the file to be debugged
which means that 'lldb -- <filename> [<ARG1> [<ARG2>]]' also works.
But remember to end the options with "--" if any of your arguments have a "-" in them.
Reproduction
Is the bug reproducible? Always
Reproduction steps:
- Open GIMP
- Watch it crash
…
Expected result:
Actual result:
Additional information
If you have a backtrace for a crash or a warning, paste it here.