[Digikam-users] Crash using Editing Tool "Hue, Saturation, & Lightness

[Gilles Caulier]

2014-02-09 22:17 GMT+01:00 DHL <sawtm at verizon.net>:
> Thank you, Gilles, for your kind reply. I found the binary DK file as you
> specified. Clicking the file opens Dk and a terminal window with lots of
> data (see attached). At the cue on the terminal window, do I enter
> "/Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam" or is dk
> running under GDB when I use the binary file to open DK?
> At http://www.digikam.org/contrib there is reference:

You need to run the digiKam binary through GDB binary to call it in a
terminal as i psecified previously :

gdb /Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam


>
> "If you found a context to crash digiKam, you can provide a backtrace using
> GDB debugger. digiKam needs to be compiled with all debug info orelse the
> backtrace will be useless. If you installed digiKam using the packages
> provided by your distribution please install the corresponding debug
> package. To find the name of these packages more information can be found
> here (((( this does not lead anywhere)))). In order to test recent changes
> made by the developers, it would be even better to build the current
> development version yourself, the instructions are given here.  (( I don't
> understand what to do here))))"
>
> To make a backtrace with GDB use following command:   DO I ENTER THIS DIALOG
> INTO TERMINAL WHEN DK CRASHES??
>
> $ gdb digikam
> (gdb) run
> (gdb) ...
> (gdb) _crash here_
> (gdb) ...
> (gdb) bt
> (gdb) _the backtrace is here_
> (gdb) quit

and after to use gdb prompt to

1/ run digikam
2/ you use digiKam and it crash.
3/ gdb will be stopped at crash
4/ you call "bt" gdb command in gdb prompt
5/ you see the internal digiKam call trace that we need. Just copy and
paste data in terminal in this file...

Gilles Caulier