Re: [RFA] bpstat_do_actions in one place

[Eli Zaretskii <eliz@gnu.org>]

> Date: Mon, 5 May 2008 15:23:15 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Vladimir Prus <vladimir@codesourcery.com>,
> 	gdb-patches@sources.redhat.com
> 
> On Mon, May 05, 2008 at 10:17:26PM +0300, Eli Zaretskii wrote:
> > > From: Vladimir Prus <vladimir@codesourcery.com>
> > > Date: Mon, 5 May 2008 16:58:31 +0400
> > > Cc: gdb-patches@sources.redhat.com
> > > 
> > > Is there any documentation for how
> > > 'quit' should generally work, especially inside breakpoint commands?
> > 
> > "quit" is documented to exit GDB.  What else is there to say?
> 
> Sorry, quit at the "hit enter for more" prompt, not the quit command.

    Certain commands to GDB may produce large amounts of information output
    to the screen.  To help you read all of it, GDB pauses and asks you for
    input at the end of each page of output.  Type <RET> when you want to
    continue the output, or `q' to discard the remaining output.

So it "discards the remaining output".  But this `q' is not a command,
just a one-letter response (GDB doesn't care what follows the initial
`q'), just like it's sibling <RET> isn't a command, so there's no
reason to expect that it will have _any_ effect inside breakpoint
commands, or in any other context where GDB expects a command.  Am I
missing something?