Bug 167913

Summary:	Segmentation fault upon start
Product:	[Applications] digikam	Reporter:	Florian <bugzilla.kde.org>
Component:	Metadata-Engine	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	caulier.gilles
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:	7.3.0
Sentry Crash Report:

Description Florian 2008-07-31 23:02:26 UTC

Version:           0.9.4, svn Revision 840296 (using KDE 3.5.9KDE 1.2)
Installed from:    SuSE RPMsSuSE RPMs
Compiler:          gcc (SUSE Linux) 4.3.2 20080613 (prerelease) [gcc-4_3-branch revision 136744]  
OS:                Linux

I got the current svn for KDE3 (svn://anonsvn.kde.org/home/kde/branches/extragear/kde3/libs, svn://anonsvn.kde.org/home/kde/branches/extragear/kde3/graphics/, svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin), compiled and installed libs & digikam and tried to start the application. It exited with a segmentation fault without any other output.

configure settings: ./configure --prefix=/usr/local/digikam_svn --with-extra-includes=/usr/local/digikam_svn/include --with-extra-libs=/usr/local/digikam_svn/lib --enable-debug=full

After installing, I set KDEDIRS to /usr/local/digikam_svn:/opt/kde3 and restarted KDE.

The backtrace is very terse:

$ gdb /usr/local/digikam_svn/bin/digikam
GNU gdb 6.6.50.20070726-cvs
Copyright (C) 2007 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/local/digikam_svn/bin/digikam
[Thread debugging using libthread_db enabled]
[New Thread 0xb58dc6d0 (LWP 25508)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb58dc6d0 (LWP 25508)]
0xb597bf49 in Exiv2::IfdInfo::IfdInfo () from /usr/lib/libexiv2.so.0
(gdb) bt
#0  0xb597bf49 in Exiv2::IfdInfo::IfdInfo () from /usr/lib/libexiv2.so.0
#1  0xb597c5f9 in ?? () from /usr/lib/libexiv2.so.0
#2  0xb599a1a5 in ?? () from /usr/lib/libexiv2.so.0
#3  0xb59d0ff4 in ?? () from /usr/lib/libexiv2.so.0
#4  0xb59d9018 in ?? ()
#5  0xbfd73bb8 in ?? ()
#6  0xb5912198 in _init () from /usr/lib/libexiv2.so.0
Backtrace stopped: frame did not save the PC
(gdb) cont
Continuing.

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) quit

Comment 1 caulier.gilles 2008-07-31 23:06:47 UTC

Crash appear in libexiv2 not digiKam

Backtrace is not suitable (no debug info).

Check your system

Gilles Caulier

Comment 2 Florian 2008-08-01 00:00:27 UTC

Thx for the hint. There was a version mismatch; has been solved.

Comment 3 Andreas Huggel 2008-08-01 10:56:30 UTC

What version of exiv2 do you have? Do you also get a segfault if you run exiv2 (the command line tool) over your images? (something like $ exiv2 -pt *) If you do, please send me the image which causes it (ahuggel at gmx dot net)

Thanks,
Andreas

Comment 4 caulier.gilles 2021-05-04 06:01:07 UTC

Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4