[Digikam-devel] [Bug 134999] crash in exiv2 when searching for new images

Marcel Wiesweg marcel.wiesweg at gmx.de
Wed Oct 4 15:10:27 BST 2006


------- 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=134999         




------- Additional Comments From marcel.wiesweg gmx de  2006-10-04 16:10 -------
The valgrind output suggests a problem with Qt's codec (but we must not forget that the codec operates on std::string data supplied by libexiv2, so if we pass invalid data that could be the reason.)

The backtraces at comment #7 and #6 happen during a delete operation in exiv2, the backtrace from 135051 when a std::string is deleted.
These crashes on delete might suggest that somewhere heap management memory is overwritten.

If the crash is reproducible for someone, could you comment out the lines as Gilles said and check if it solves the problem?
Janet, otherwise, can you perhaps provide a valgrind report?



More information about the Digikam-devel mailing list