Created attachment 161385 [details] This depicts the problem. STEPS TO REPRODUCE 1. Cause https://bugs.kde.org/show_bug.cgi?id=474115#c0 2. Show trace. OBSERVED RESULT It is unable to generate the trace. https://discuss.kde.org/t/how-to-prevent-drkonqi-automatically-rejecting-debuginfo-package-download/4697?u=rokejulianlockhart provide some relevant information. EXPECTED RESULT The trace should generate, or there should at least be an error. See attached screenshot. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230828 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.4.11-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 46.9 GiB of RAM Graphics Processor: AMD Radeon RX 5700
A possibly relevant merge request was started @ https://invent.kde.org/plasma/drkonqi/-/merge_requests/261
Git commit 34cc1171c26d72dc423cbe0f10d03ac541b3d1e6 by Harald Sitter. Committed on 27/08/2024 at 11:24. Pushed by sitter into branch 'master'. backtracegenerator: cache raw debugger output and give the user access to it this now means we capture both stdout and stderr. shouldn't be a huge problem because we ultimately run the output through the gdb parser anyway and that filters out most of the noise. plus, we mostly care about the traces in sentry anyway and those are generated by the preamble and clean. there are two ways to get the data - the inlinemessage now sports a details link that opens a txt file - via the developer view, which no longer shows a useless error there area also now verbosity lines to mark the beginning and the end of the debugging session Related: bug 477586, bug 478110, bug 491820 M +53 -2 src/backtracegenerator.cpp M +7 -0 src/backtracegenerator.h M +2 -3 src/qml/DeveloperPage.qml M +16 -1 src/qml/main.qml https://invent.kde.org/plasma/drkonqi/-/commit/34cc1171c26d72dc423cbe0f10d03ac541b3d1e6