https://bugs.kde.org/show_bug.cgi?id=440113
Bug ID: 440113
Summary: drkonqi could not start debugger: "gdb"
Product: drkonqi
Version: unspecified
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: backtraceparsing
Assignee: plasma-b...@kde.org
Reporter: ralf.habac...@freenet.de
Blocks: 426400
Target Milestone: ---
STEPS TO REPRODUCE
1. On Windows download portable kmymoney snapshot from
https://kmymoney.org/snapshots.php#kmymoney5-aq6
2. download debugview from
https://docs.microsoft.com/en-us/sysinternals/downloads/debugview
3. start dbgview
4. unpack archive with 7z and open windows command shell at the unpackaged root
dir
5. enter
set QT_LOGGING_RULES=*drkonqi*.debug=true
6. enter
start.bat
7. close kmymoney
8. after kmymoney crashed and drkonqi comes up, open drop down box named
"debugging" and click at "debugging in gdb".
OBSERVED RESULT
In dbgview you will see messages like
org.kde.drkonqi: Could not start debugger: "gdb"
EXPECTED RESULT
That message should not appear; instead gdb should has been started
SOFTWARE/OS VERSIONS
Windows: 10
KDE Frameworks Version: 5.65.0
Qt Version: 5.11
ADDITIONAL INFORMATION
At
https://invent.kde.org/plasma/drkonqi/-/blob/master/src/data/debuggers/external/gdbrc#L78
you can see that the drkonqi configuration uses "Konsole" for the application,
which is not available on Windows and need to be fixed.
Referenced Bugs:
https://bugs.kde.org/show_bug.cgi?id=426400
[Bug 426400] Fix KF5 issues on Windows
--
You are receiving this mail because:
You are watching all bug changes.
