Bug 56478 - User should be able to specify an external non-gdb debugger
Summary: User should be able to specify an external non-gdb debugger
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-27 06:15 UTC by Paul Hoepfner-Homme
Modified: 2006-01-24 10:16 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Hoepfner-Homme 2003-03-27 06:15:43 UTC 
Version:           unknown (using KDE 3.1.0)
Compiler:          gcc version 2.95.3 20010315 (release)
OS:          Linux (i686) release 2.4.19-pre7

I would like to use Kdbg for my debugger since it works so well for me, but KDevelop doesn't seem to provide such an option to me. If I specify "/usr/bin/kdbg" for the "Debugger shell" field in the Project Options, I get an error from kdbg about an invalid argument. So KDevelop seems to expect only gdb-compatible debuggers in that field. I think it would be nice to give users who have trouble using KDevelop's built-in debugging interface (like me) a way to run their own external debugger application, such as Kdbg (rather than a gdb-style shell debugger).
Comment 1 Vladimir Prus 2006-01-24 10:16:27 UTC 
I'm sorry, I don't think how running kdbg from KDevelop is better than running kdbg separately (say, from Alt-F2). Supporting running external GUI debugger will sure complicate the code for little benefit.