SUMMARY: More specifically, I mean that installation of the GNU Debugger (rather than mere presence, which is what installation is able to mean) does not allow DrKonqi to generate traces, despite the sole instruction that DrKonqi provides if the GNU Debugger is not present being to merely "install gdb", and no way for DrKonqi to be reinitalised without subsequent occurrence of the error that caused initial initialisation of DrKonqi. STEPS TO REPRODUCE: 1. Experience crash. 2. Click the button whose label is “Report Bug” that DrKonqi provides. 3. Observe that DrKonqi is unable to generate traces because the GNU Debugger is not present. 4. Install the GNU Debugger. 5. Observe that DrKonqi is unable to generate traces despite the presence of the GNU Debugger. 6. Experience the crash again if the crash is luckily possible to consistently reproduce. 7. Click the button whose label is “Report Bug” that DrKonqi provides. OBSERVED RESULT: 8. DrKonqi is able to generate traces. EXPECTED RESULT: 3. Generation of the trace by DrKonqi. SOFTWARE/OS VERSIONS: Windows: Unknown. macOS: Unknown. Linux/KDE Plasma: Positive. KDE Plasma Version: “5.24.5”. KDE Frameworks Version: “5.94.0”. Qt Version: “5.15.4”. ADDITIONAL INFORMATION: Addition of "http://bugs.kde.org/show_bug.cgi?id=245992" would have assisted remediation of this problem, so I suggest that it be implemented to assist subsequent diagnosis. I have labelled this problem as "crash" because I recall that DrKonqi stated paraphrasally that the GNU Debugger has crashed.
Cannot reproduce. When gdb is missing the output isn't that it crashed and when I install it and click the reload button it correctly creates a trace. What am I missing? Is your problem reproducible at all? You can force any application to crash by running `killall -SEGV kwrite` or some other name.
(In reply to Harald Sitter from comment #1) > Cannot reproduce. When gdb is missing the output isn't that it crashed and > when I install it and click the reload button it correctly creates a trace. > What am I missing? > > Is your problem reproducible at all? You can force any application to crash > by running `killall -SEGV kwrite` or some other name. You shall need to wait some time before I am able to potentially reproduce this again, because DrKonqi was recently rewritten in Kirigami, and updates to Fedora may have remediated this, and I shall need to configure a new system without GDB and cause an error that DrKonqi notices to evaluate whether this continues to occur.
(In reply to BEEDELL ROKE JULIAN LOCKHART from comment #2) > (In reply to Harald Sitter from comment #1) > > Cannot reproduce. When gdb is missing the output isn't that it crashed and > > when I install it and click the reload button it correctly creates a trace. > > What am I missing? > > > > Is your problem reproducible at all? You can force any application to crash > > by running `killall -SEGV kwrite` or some other name. > > You shall need to wait some time before I am able to potentially reproduce > this again, because DrKonqi was recently rewritten in Kirigami, and updates > to Fedora may have remediated this, and I shall need to configure a new > system without GDB and cause an error that DrKonqi notices to evaluate > whether this continues to occur. Sorry. I didn't read your comment at all. It works now.