<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Caulier Gilles schrieb:
<blockquote cite="mid200608282056.16965.caulier.gilles@kdemail.net"
type="cite">
<pre wrap="">Le Lundi 28 Août 2006 17:56, Duncan Hill a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">efpost wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I can't give any specific error messages, because the crash just evokes
the KDE-Crashmanager with Signal 11 (SIGSEGV). Back trace is not
possible.
</pre>
</blockquote>
<pre wrap="">For the compiled version, use this:
./configure --enable-debug=full
Then invoke digikam from the command line. a) you'll get console
output, and b) you'll get a full core in the kde crash handler.
_______________________________________________
Digikam-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Digikam-users@kde.org">Digikam-users@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/digikam-users">https://mail.kde.org/mailman/listinfo/digikam-users</a>
</pre>
</blockquote>
<pre wrap=""><!---->
Look in HACKING file. There are instructions to report a backtrace using GDB
Gilles Caulier
_______________________________________________
Digikam-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Digikam-users@kde.org">Digikam-users@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/digikam-users">https://mail.kde.org/mailman/listinfo/digikam-users</a>
</pre>
</blockquote>
I did. But entering "gdb digikam" into console gives <br>
<br>
bash: gdb: command not found.<br>
<br>
Udo<br>
</body>
</html>