[Digikam-users] digikam 0.9 keeps crashing

[efpost]

Caulier Gilles schrieb:

>Le Lundi 28 Août 2006 10:49 PM, efpost a écrit :
>  
>
>>efpost schrieb:
>>    
>>
>>>Caulier Gilles schrieb:
>>>      
>>>
>>>>Le Lundi 28 Août 2006 17:56, Duncan Hill a écrit :
>>>>        
>>>>
>>>>>efpost wrote:
>>>>>          
>>>>>
>>>>>>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.
>>>>>>            
>>>>>>
>>>>>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.
>>>>>_______________________________________________
>>>>>          
>>>>>
>>>>Look in HACKING file. There are instructions to report a backtrace using
>>>>GDB
>>>>
>>>>Gilles Caulier
>>>>_______________________________________________
>>>>        
>>>>
>>>I did. But entering "gdb digikam" into console gives
>>>
>>>bash: gdb: command not found.
>>>
>>>Udo
>>>      
>>>
>>----------------------------
>>
>>Sorry,
>>I had to install gdb first (never used a debugger before)
>>
>>Now I have the following backtrace from kde crah handler. Situation was
>>type 1 of my first post (clean start into existing database directory)
>>
>>
>>Using host libthread_db library "/lib/tls/libthread_db.so.1".
>>[Thread debugging using libthread_db enabled]
>>[New Thread -1241233728 (LWP 26873)]
>>[KCrash handler]
>>#5  0xb60e62ad in mallopt () from /lib/tls/libc.so.6
>>#6  0xb60e6942 in free () from /lib/tls/libc.so.6
>>#7  0xb628a4e1 in operator delete () from /usr/lib/libstdc++.so.6
>>#8  0xb62661ed in std::string::_Rep::_M_destroy ()
>>   from /usr/lib/libstdc++.so.6
>>#9  0xb6268d58 in std::basic_string<char, std::char_traits<char>,
>>std::allocator<char> >::~basic_string () from /usr/lib/libstdc++.so.6
>>#10 0xb7e4541b in Digikam::DMetadata::convertCommentValue (
>>    exifDatum=@0x815b134) at dmetadata.cpp:1006
>>#11 0xb7e460f1 in Digikam::DMetadata::getImageComment (this=0xbf827488)
>>    at dmetadata.cpp:850
>>#12 0xb7ce8dab in Digikam::ScanLib::storeItemInDatabase (this=0xbf8277e8,
>>    albumURL=@0xbf827528, filename=@0xbf827574, albumID=2) at
>>scanlib.cpp:397
>>#13 0xb7ce9308 in Digikam::ScanLib::allFiles (this=0xbf8277e8,
>>    directory=@0xbf827680) at scanlib.cpp:350
>>#14 0xb7ce941a in Digikam::ScanLib::allFiles (this=0xbf8277e8,
>>    directory=@0xbf827720) at scanlib.cpp:355
>>#15 0xb7ce9fea in Digikam::ScanLib::findMissingItems (this=0xbf8277e8)
>>    at scanlib.cpp:191
>>#16 0xb7cea56f in Digikam::ScanLib::startScan (this=0xbf8277e8)
>>    at scanlib.cpp:91
>>#17 0xb7c8af92 in Digikam::AlbumManager::setLibraryPath (this=0x8128fc0,
>>    path=@0xbf8279e8) at albummanager.cpp:289
>>#18 0x0804a85c in main (argc=-1209025432, argv=0xb61b0420) at main.cpp:243
>>
>>
>>Appreciate your help.
>>Udo
>>    
>>
>
>This problem have been corrected in current implementation. If you use the 
>0.9.0-beta1, i'm so surprise, because i think it have been fixed just before 
>beta1 release.
>
>I all case, current implementation from svn repository is the utimate 
>solution. Look in digiKam web site how to download source code from svn and 
>how to compile it.
>
>Gilles
>			
> <http://prdownloads.sourceforge.net/digikam/digikam-0.9.0-beta1-r1.tar.bz2?download>
>
Thanks for the quick answer, Gilles. I had downloaded
digikam-0.9.0-beta1-r1.tar.bz2 
<http://prdownloads.sourceforge.net/digikam/digikam-0.9.0-beta1-r1.tar.bz2?download>from
sourceforge.net as indicated at the digikam-website.
Now I'll try the svn version and will report here tomorrow.

Thanks again.
Udo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20060828/532bbb54/attachment.html>