Bug 440113 - drkonqi could not start debugger: "gdb"
Summary: drkonqi could not start debugger: "gdb"
Status: REPORTED
Alias: None
Product: drkonqi
Classification: Applications
Component: backtraceparsing (show other bugs)
Version: unspecified
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks: 426400
  Show dependency treegraph
 
Reported: 2021-07-21 14:26 UTC by Ralf Habacker
Modified: 2021-08-05 00:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Habacker 2021-07-21 14:26:10 UTC
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.
Comment 1 Ralf Habacker 2021-07-28 06:50:43 UTC
See https://invent.kde.org/plasma/drkonqi/-/merge_requests/36 for an associated merge request