Bug 76043

Summary:	Provide facility to enter gdb command line options
Product:	[Applications] kdevelop	Reporter:	David Jarvie <djarvie>
Component:	CPP Debugger	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED NOT A BUG
Severity:	wishlist
Priority:	NOR
Version First Reported In:	3.0.0
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description David Jarvie 2004-02-24 18:18:56 UTC

Version:           3.0 (using KDE KDE 3.2.0)
Installed from:    Compiled From Sources
OS:          Linux

I need to set the --nofork option for gdb, since my program is a KUniqueApplication. I can't see how I can specify this. In KDevelop 2, I used to select "Debug with options" (if I remember correctly) to debug the program, which would prompt to enter any gdb options. But this doesn't exist any more in KDevelop 3.0. And the Project Options dialog also doesn't seem to have anywhere to specify this.

Comment 1 David Jarvie 2004-02-24 22:12:19 UTC

I think that perhaps --nofork is a KDE program argument rather than a debugger one. However, even though I entered --nofork in the "Program arguments" field in the Project Options Debugger tab, it didn't show up in the GDB output tab when I started the debug session.

Comment 2 Amilcar do Carmo Lucas 2004-02-24 22:37:00 UTC

> --nofork in the "Program arguments" field in the Project Options Debugger tab
Sorry that one does not work.
use program arguments of the "Run Options" dialog instead.

Comment 3 Vladimir Prus 2005-08-19 10:33:54 UTC

The original report was in fact about program arguments, not gdb arguments, and that problem does not exist. The "gdb argument" problem is bug 84251. Closing this one.