Bug 84251 - gdb call cannot be configured
Summary: gdb call cannot be configured
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: 3.0.4
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-30 11:31 UTC by Robert Vogl
Modified: 2008-06-29 20:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Vogl 2004-06-30 11:31:27 UTC 
Version:           3.0.4 (using KDE KDE 3.2.1KDE 1.2)
Installed from:    Compiled From SourcesCompiled From Sources
OS:                Linux

There is no possibility to configure the embedded call of the gdb. The only way to alter the initial gdb commands is to hack the source (gdbcontroller.cpp). I think this should be made configurable by a configuration file (e.g. if I would like gdb to ignore a SIGUSR1 signal.)

Also the command line arguments delivered by the internal gdb call are not configurable.

The gdb call should be more flexible.

It is desirable to enhance the already existing project specific configuration dialog.
Comment 1 Andreas Pakulat 2008-06-29 20:20:52 UTC 
you can provide your own shell to start gdb via the gdb options. You can execute any gdb command in your .gdbinit file. So IMHO this is fixed.