>$ darktable --library :memory:
0.0000 [dt starting]
darktable --library :memory:
an error occurred while trying to execute gdb. please check if gdb is installed on your system.
backtrace written to /tmp/darktable_bt_7FEOK3.txt
Segmentation fault
the file darktable_bt_7FEOK3.txt does not exist in /tmp or any other directory.
gdb (the debugger) is not installed on my system.
I was trying to look at an image and I didn’t want that new image into my catalog.
>$ darktable
just dt w/o any parameter and absolutely no problem.
It might be irrelevant, but I once had Norton antivirus software remove the darktable file gdbus.exe, following a false positive. It should exist in the bin folder.
In older Linux systems you had to add ulimit -c unlimited to system init files to enable core dumps. I’m not sure if the procedure has changed, but the process can think it’s making a dump file even though the system doesn’t allow it.