Summary: | crash on thumb generation, large tiff's | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | ejovrh <hrvoje.ivanic> |
Component: | Thumbs-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, hrvoje.ivanic |
Priority: | NOR | ||
Version: | 3.1.0 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.1.0 | |
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
ejovrh
2013-05-25 09:05:24 UTC
Please follow the guide[1] and try to provide a better backtrace, since you can reproduce the crash every time. [1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash Created attachment 80064 [details]
New crash information added by DrKonqi
digikam (3.1.0) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2
- What I was doing when the application crashed:
scan as before, this time with installed libstdc++ dbg package
please advise on the missing dbg symbols.
feel free to contact me to reproduce more.
-- Backtrace (Reduced):
#9 0xb4be228d in __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
#10 0xb4bdfef3 in __cxxabiv1::__terminate (handler=0xb4be2140 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:40
#11 0xb4bdff2f in std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:50
#12 0xb4be0225 in __cxxabiv1::__cxa_rethrow () at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:116
#13 0xb4d5eae2 in QThreadPoolThread::run (this=0xaa0dd58) at concurrent/qthreadpool.cpp:114
@ejovrh, please read comment #1. Drkonqi can't generate a useful backtrace in your case. You have to run digikam under gdb. In fact we need the place where the exception is thrown. That means you need to run digikam under gdb, interrupt, "catch throw", provoke the crash, and get the backtrace. Yes, just follow the guide given in comment #1. New digiKam 4.11.0 is available with official PKG installer for OSX. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. Gilles Caulier With digiKam 5.0.0, this problem is not reproducible. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier |