Bug 509440 - drkonqi tries to access invalid memory and crashes the bugreport
Summary: drkonqi tries to access invalid memory and crashes the bugreport
Status: RESOLVED UPSTREAM
Alias: None
Product: drkonqi
Classification: Applications
Component: backtraceparsing (other bugs)
Version First Reported In: 6.4.4
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-12 22:38 UTC by Ángel Navarro
Modified: 2025-09-15 11:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
dkonqi autocrash log (2.79 KB, text/plain)
2025-09-12 22:38 UTC, Ángel Navarro 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ángel Navarro 2025-09-12 22:38:37 UTC 
Created attachment 184922 [details]
dkonqi autocrash log

SUMMARY
The attached log explains itself. I tried to report a Kate bug where it crashed when a file was modified on disk and the bugreport process also crashed. I do have automatic debug symbol download enable and retried multiple times with no luck.

STEPS TO REPRODUCE
This may not be reproducible because it chains one bug with another. Read the drkonqi log.

OBSERVED RESULT
Bugreporting backtrace step failed due to it trying to access invalid memory.

EXPECTED RESULT
Bugreport backtrace should contitue normally.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION
Comment 1 Harald Sitter 2025-09-15 11:36:47 UTC 
Unfortunately there's nothing we can do when the core fails to parse correctly. We need frame addresses to resolve the backtrace, if they are not present the backtrace is useless.