| Summary: | drkonqi tries to access invalid memory and crashes the bugreport | ||
|---|---|---|---|
| Product: | [Applications] drkonqi | Reporter: | Ángel Navarro <jesusnavarrojr188> |
| Component: | backtraceparsing | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | sitter |
| Priority: | NOR | ||
| Version First Reported In: | 6.4.4 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | dkonqi autocrash log | ||
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. |
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