https://bugs.kde.org/show_bug.cgi?id=214188
Christophe Giboudeaux <cgiboude...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEEDSINFO
Resolution| |BACKTRACE
--- Comment #1 from Christophe Giboudeaux <cgiboudeaux gmail com> 2009-11-12
09:49:48 ---
Unfortunately, we can't conclude anything from your backtrace.
If you experience this freeze again, you may try that:
- find the process id of kmail: pidof kmail
- attach gdb to this process: gdb kmail pid (where 'pid' is the number you got
above)
- When the debug symbols are loaded: thread apply all backtrace
More details on this page:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB
Also, 'reason unknown' is not very helpful. What were you doing before? How did
you see that KMail froze? Any clue is important.
Thanks.
Changing the bug status, please change it back to 'unconfirmed' if you get more
informations.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
