Summary: | Kontact crashed at the end of automatic filtering messages in the inbox | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Andrzej Porretta-Tomaszewski <dakhan_t> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | kdenis |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Andrzej Porretta-Tomaszewski
2012-01-22 09:18:19 UTC
(In reply to comment #0) > The crash can be reproduced every time. > Please try the following steps to get a backtrace of the real issue: 1/ R gdb --args kontact --nofork &> ~/bug292168.txt 2/ When the gdb prompt "(gdb)" appears, enter: - "set logging file ~/bug292168.txt" - "set logging on" - "start" and wait for the prompt to reappear, then enter "break __cxa_rethrow" and finally "cont" to let the window appear. 3/ Reproduce the crash. If kontact crashes, the window will appear frozen. That's normal. 4/ in the konsole window, run "thread apply all bt" if you're prompted to continue, press enter 5/ and finally, when the "(gdb)" prompt reappears, enter "kill" then "quit" You will then find a bug292168.txt file in your home directory. Please attach it to this report. I added a new section to summarize what to do: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash changing status Closing due to lack of feedback |