[Digikam-devel] [Bug 152092] showfoto crashes ( signal 11 ) on exit

Gilles Caulier caulier.gilles at gmail.com
Fri May 16 07:15:26 BST 2008


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=152092         




------- Additional Comments From caulier.gilles gmail com  2008-05-16 08:15 -------
Arnd,

With valgrind, showfoto do not crash, but it report this trace :

==31266== Invalid read of size 4
==31266==    at 0x5260CE0: QImage::~QImage() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.8)
==31266==    by 0x5FC06C3: exit (in /lib/i686/libc-2.7.so)
==31266==    by 0x5FAA397: (below main) (in /lib/i686/libc-2.7.so)
==31266==  Address 0x8ef9f08 is 0 bytes inside a block of size 64 free'd
==31266==    at 0x402105C: operator delete(void*) (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==31266==    by 0x5260D08: QImage::~QImage() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.8)
==31266==    by 0x5FC06C3: exit (in /lib/i686/libc-2.7.so)
==31266==    by 0x5FAA397: (below main) (in /lib/i686/libc-2.7.so)
==31266==
==31266== Invalid write of size 4
==31266==    at 0x5260CE7: QImage::~QImage() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.8)
==31266==    by 0x5FC06C3: exit (in /lib/i686/libc-2.7.so)
==31266==    by 0x5FAA397: (below main) (in /lib/i686/libc-2.7.so)
==31266==  Address 0x8ef9f08 is 0 bytes inside a block of size 64 free'd
==31266==    at 0x402105C: operator delete(void*) (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==31266==    by 0x5260D08: QImage::~QImage() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.8)
==31266==    by 0x5FC06C3: exit (in /lib/i686/libc-2.7.so)
==31266==    by 0x5FAA397: (below main) (in /lib/i686/libc-2.7.so)

Look like the gdb backtrace reported before ask than a delete operator crash showfoto. This valgrind report appears just after to quit. Sound like it's the problem...

...but my valgrind backtrace is not really suitable here. Can you make a better one, with the source code relevant where the delete operator is processed ?

Gilles



More information about the Digikam-devel mailing list