This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA] bpstat_do_actions in one place


On Wed, May 07, 2008 at 03:55:42PM +0300, Eli Zaretskii wrote:
> > On Wed, May 07, 2008 at 11:02:38AM +0300, Eli Zaretskii wrote:
> > > That this instance of `backtrace' be aborted, and the loop will
> > > continue.
> > 
> > Interesting.  That's not what I would expect; for instance, I'd
> > expect an entire user-defined ("define") command to be aborted.
> 
> What user-defined command?  The example was about breakpoint commands,
> not about a user-defined command defined by "define", wasn't it?

They're all the same mechanism.  For instance,

define sillybt
backtrace
backtrace
end

If q should stop backtrace, IMO it should stop sillybt too.

> > If that happened, how would you stop the example I gave?
> 
> How would one stop _any_ endless loop?  Ctrl-C, I guess.

But it won't work.  C-c is implemented as the exact same thing as
typing q at a pagination prompt: eventually a quit exception is
thrown.  So you will only stop the currently printing backtrace and
things will keep on going.

-- 
Daniel Jacobowitz
CodeSourcery


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]