Re: [RFA] bpstat_do_actions in one place

[Daniel Jacobowitz <drow@false.org>]

On Mon, May 05, 2008 at 04:58:31PM +0400, Vladimir Prus wrote:
> Well, this was the behaviour I though to be the most reasonable. 

OK.  If we want to change it, someone gets the lousy job of going
through all the call sites.  I had to fix up a bunch of them recently.

> > For instance, a program running in a while (1) loop with a breakpoint
> > set in it, and the breakpoint has a command that produces output, like
> > backtrace.  Quit will now resume the program and generate another
> > backtrace, I think.
> 
> Yes, I think so; seems fine to me. Is there any documentation for how
> 'quit' should generally work, especially inside breakpoint commands?

It's only a problem because there's no way to stop it.  When the
prompt is displayed C-c will not stop the application (since it's
already stopped), and typing q will stop the current backtrace and
resume the application.  Very hard to get out of it.

No, there isn't any documentation for how this should work, yet.

-- 
Daniel Jacobowitz
CodeSourcery