This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: GDB needs a --cmdline option
- To: Mo DeJong <mdejong at cygnus dot com>
- Subject: Re: GDB needs a --cmdline option
- From: Fernando Nasser <fnasser at cygnus dot com>
- Date: Thu, 11 May 2000 16:26:40 -0400
- CC: gdb-patches at sourceware dot cygnus dot com
- Organization: Red Hat , Inc. - Toronto
- References: <Pine.SOL.3.91.1000511131403.14281B-100000@cse.cygnus.com>
Mo DeJong wrote:
>
> On 11 May 2000, Tom Tromey wrote:
>
> > >>>>> "Fernando" == Fernando Nasser <fnasser@cygnus.com> writes:
> >
> > Fernando> But gdb will still read the .gdbinit file and, if you put a
> > Fernando> "b _exit" in there gdb will fire up as you want.
> >
> > Fernando> Is that acceptable?
> >
> > It seems like it wouldn't be too much work to add a `--interactive'
> > option which will do all the setup but also ensure that you get a
> > command prompt. Having an invisible mode is definitely nice. But
> > sometimes pre-editing .gdbinit is a PITA.
> >
> > Tom
>
> How about --run-noexit, I am not sure that --interactive really
> makes it clear that the option is linked to the use of the --run
> option.
>
I guess he really meant "interactive". Not exiting will do no good on
native configurations because the inferior process is gone.
What Tom wants is a way to "set args" from the command line.
This seems more like a convenience though.
The xdb style --run goes a little beyond what we currently offer.
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@cygnus.com
2323 Yonge Street, Suite #300 Tel: 416-482-2661 ext. 311
Toronto, Ontario M4P 2C9 Fax: 416-482-6299