| Summary: | "Show details" should not use cached result (but retry retracing) | ||
|---|---|---|---|
| Product: | [Applications] drkonqi | Reporter: | Daniel Hahler <kde-bugzilla> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | wishlist | CC: | finex |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | ||
It is not intended to work in this way: you've to restart the crashed software and reproduce the crash for having a full backtrace. This is rather difficult (or impossible), if the crash is not easily reproducible. As far as I understand, it could work this way, correct? Then why not do it like that? A compromise might be to only try retracing, if it failed before toggling the checkbox. |
Version: (using Devel) Installed from: Compiled sources Clicking "Show details" in the KDE Crash Handler tries to generate a backtrace. This failed for a Kopete crash now, since I had no debug packages installed. So, I went ahead, installed the debug packages and expected toggling "Show details" to retry generating the backtrace, but it appears to use the previous result ("This backtrace appears to be of no use. ...") It would be nice, if toggling (unchecking and checking again) "Show details" would not use the previous (obsolete) result.