[Digikam-devel] [Bug 250134] Digikam crashed during search for duplicates

Marcel Wiesweg marcel.wiesweg at gmx.de
Sat Sep 4 15:48:20 BST 2010


https://bugs.kde.org/show_bug.cgi?id=250134





--- Comment #6 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-09-04 16:48:20 ---
I see, digikam uses up all memory. Chances are it is std::bad_alloc thrown,
you'll see that in the console.
To set the catchpoint in gdb, the command is "catch throw".

If it is really using up memory, it will be more interesting to see where the
memory is used. Running "valgrind --tool=massif digikam" will run digikam,
albeit very slow, watching its memory usage and producing an output file
massif.out.xy.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Digikam-devel mailing list