GDB needs a --cmdline option

Fernando Nasser
Thu May 11 08:32:00 GMT 2000

Tom Tromey wrote:
> >>>>> "Fernando" == Fernando Nasser <> 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.

--interactive sounds that -run would only set the arguments and give you
the prompt (would not be a -run, but a -setargs).

Is that what you mean?

BTW, I just realized that we will have to run the target before printing
the initial messages and the first prompt, and if the program exits
without receiving a signal or a breakpoint, not to print them at all.
On the other hand, if some event happens, we must enter the command loop.

This may be tricky.  Elena, what do you think?

Fernando Nasser
Red Hat - Toronto                       E-Mail:
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299

More information about the Gdb-patches mailing list