segmentationfault from libexiv2

I compile digikam and libexiv2 from svn once or twice a week.
digikam-0.9.5_svn-853520
digikam-libs-0.9.5_svn-853516
libexiv2-4-0.17.91-1567.svn

As you can see it is exiv2 version 0.17. This places de in /usr/lib
/usr/lib/libexiv2.so -> libexiv2.so.4.0.1
/usr/lib/libexiv2.so.4 -> libexiv2.so.4.0.1
/usr/lib/libexiv2.so.4.0.1

With this configuration digikam runs smoothly without a hitch.

I also need ibexiv2.so.0. Among others it is required by qtpfsgui.
So I install libexiv2-0.15-8.2 form the opensuse repos. It gives me
/usr/lib/libexiv2.so.0 -> libexiv2.so.0.1.0
/usr/lib/libexiv2.so.0.1.0

But now digikam crashes with a reference to libexiv2.so.0. This is what
puzzles me because I compiled digikam against the other version.

This is what gdb gives me as I just point the mouse at an image:

(gdb) run
Starting program: /opt/kde3/bin/digikam
[Thread debugging using libthread_db enabled]
[New Thread 0xb58b56d0 (LWP 6774)]
Found dcraw version: 8.87
[New Thread 0xb5281b90 (LWP 6794)]
[New Thread 0xb4a80b90 (LWP 6795)]
[Thread 0xb5281b90 (LWP 6794) exited]
[Thread 0xb4a80b90 (LWP 6795) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb58b56d0 (LWP 6774)]
0xb28fd939 in Exiv2::TypeInfoTable::TypeInfoTable ()
from /usr/lib/libexiv2.so.0
(gdb) bt
#0  0xb28fd939 in Exiv2::TypeInfoTable::TypeInfoTable ()
from /usr/lib/libexiv2.so.0
#1  0xb28fde9c in ?? () from /usr/lib/libexiv2.so.0
#2  0xb29041a5 in ?? () from /usr/lib/libexiv2.so.0
#3  0xb293aff4 in ?? () from /usr/lib/libexiv2.so.0
#4  0x0848c080 in ?? ()
#5  0xbfdaa9d8 in ?? ()
#6  0xb287c198 in _init () from /usr/lib/libexiv2.so.0
Backtrace stopped: frame did not save the PC
(gdb) quit

After uninstalling libexiv2-0.15-8.2 everything works fine.

Is this a bug in digikam?

Caspar.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2008/8/28 Caspar Maessen <[hidden email]>:

> I compile digikam and libexiv2 from svn once or twice a week.
> digikam-0.9.5_svn-853520
> digikam-libs-0.9.5_svn-853516
> libexiv2-4-0.17.91-1567.svn
>
> As you can see it is exiv2 version 0.17. This places de in /usr/lib
> /usr/lib/libexiv2.so -> libexiv2.so.4.0.1
> /usr/lib/libexiv2.so.4 -> libexiv2.so.4.0.1
> /usr/lib/libexiv2.so.4.0.1
>
> With this configuration digikam runs smoothly without a hitch.
>
> I also need ibexiv2.so.0. Among others it is required by qtpfsgui.
> So I install libexiv2-0.15-8.2 form the opensuse repos. It gives me
> /usr/lib/libexiv2.so.0 -> libexiv2.so.0.1.0
> /usr/lib/libexiv2.so.0.1.0
>
> But now digikam crashes with a reference to libexiv2.so.0. This is what
> puzzles me because I compiled digikam against the other version.
>
> This is what gdb gives me as I just point the mouse at an image:
>
> (gdb) run
> Starting program: /opt/kde3/bin/digikam
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb58b56d0 (LWP 6774)]
> Found dcraw version: 8.87
> [New Thread 0xb5281b90 (LWP 6794)]
> [New Thread 0xb4a80b90 (LWP 6795)]
> [Thread 0xb5281b90 (LWP 6794) exited]
> [Thread 0xb4a80b90 (LWP 6795) exited]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb58b56d0 (LWP 6774)]
> 0xb28fd939 in Exiv2::TypeInfoTable::TypeInfoTable ()
> from /usr/lib/libexiv2.so.0
> (gdb) bt
> #0  0xb28fd939 in Exiv2::TypeInfoTable::TypeInfoTable ()
> from /usr/lib/libexiv2.so.0
> #1  0xb28fde9c in ?? () from /usr/lib/libexiv2.so.0
> #2  0xb29041a5 in ?? () from /usr/lib/libexiv2.so.0
> #3  0xb293aff4 in ?? () from /usr/lib/libexiv2.so.0
> #4  0x0848c080 in ?? ()
> #5  0xbfdaa9d8 in ?? ()
> #6  0xb287c198 in _init () from /usr/lib/libexiv2.so.0
> Backtrace stopped: frame did not save the PC
> (gdb) quit
>
> After uninstalling libexiv2-0.15-8.2 everything works fine.
>
> Is this a bug in digikam?

No. but i recommend to try the current libkexiv2 interface from KDE3
branch where i have reduced all depencies to exiv2.

Best

Gilles Caulier
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Op donderdag 28 augustus 2008, schreef Gilles Caulier:

  > 2008/8/28 Caspar Maessen <[hidden email]>:
  > > Is this a bug in digikam?
  >
  > No. but i recommend to try the current libkexiv2 interface from KDE3
  > branch where i have reduced all depencies to exiv2.

Recompiled just now. No luck. Digikam crashes with the same gdb-output.


Caspar.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Hum, it sound like another problem with Exiv2

Are you tried to ask on Exiv2 mailing list ? Andreas Huggel can
investiguate better than me...

Gilles Caulier

2008/8/28 Caspar Maessen <[hidden email]>:

> Op donderdag 28 augustus 2008, schreef Gilles Caulier:
>
>  > 2008/8/28 Caspar Maessen <[hidden email]>:
>  > > Is this a bug in digikam?
>  >
>  > No. but i recommend to try the current libkexiv2 interface from KDE3
>  > branch where i have reduced all depencies to exiv2.
>
> Recompiled just now. No luck. Digikam crashes with the same gdb-output.
>
>
> Caspar.
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users