GDB needs a --cmdline option
Thu May 11 13:29:00 GMT 2000
Eli Zaretskii wrote:
> > Date: Thu, 11 May 2000 11:32:31 -0400
> > From: Fernando Nasser <firstname.lastname@example.org>
> > 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?
> Disabling the initial messages means --run will imply --quiet.
Good catch. Yes, we could do that. But if we ever get interactive we may
want to be non-quiet again.
> Entering the command loop does not necessarily mean that the initial
> messages need to be printed at that time.
> Does this solve the problem?
I am concerned with the prompt (actually, the read from stdin).
Red Hat - Toronto E-Mail: email@example.com
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