Bug 127407

Summary:	let kcrash write the backtrace to a log file
Product:	[Applications] drkonqi	Reporter:	Carsten Lohrke <carstenlohrke>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	wishlist	CC:	jg, l.lunak
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Carsten Lohrke 2006-05-16 01:15:09 UTC

Version:            (using KDE KDE 3.5.2)
Installed from:    Compiled From Sources

Lately it happened once again: I closed KDE and X hang. Switching to cmd revealed that kicker crashed and kcrash was waiting for input. I killed kcrash and X exited. But of course I can't write a report, because the backtrace is gone...

Comment 1 jg 2006-08-31 00:31:57 UTC

One idea would be for the Crash Handler to by default write the log to your ~/ or /tmp and display the location of this file on TTY to cover these situations.

Unless you can reproduce the kicker crash, then maybe you can fake it in a normal X session shutting down so you can see the backtrace.

Alternatively, is there no way to attatch gdb to the crashed kicker process to grab the backtrace from the TTY?

Just ideas! Mabye you guys have other suggestions.

Comment 2 Lubos Lunak 2008-01-22 15:42:05 UTC

DrKonqi has a button for saving the backtrace.