https://bugs.kde.org/show_bug.cgi?id=515630
--- Comment #4 from Harald Sitter <[email protected]> --- Not wrong per se. drkonqi cannot trace a crash that has a deleted mapping because we have no way of knowing if the new file on disk is same-ish enough to the old file to have the trace make sense. It's a guard rail to prevent reporting crashes with nonsense frames or crashes that were caused by doing a live update. That said, a manually invoked gdb will still happily trace things, it just may end up saying the crash involved frame foo when in fact it involved bar (because the two changed places in the new binary) -- You are receiving this mail because: You are watching all bug changes.
