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


> Date: Wed, 7 May 2008 07:37:36 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: vladimir@codesourcery.com, gdb-patches@sources.redhat.com
> 
> 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?

> If that happened, how would you stop the example I gave?

How would one stop _any_ endless loop?  Ctrl-C, I guess.

Anyway, I don't think `q's behavior should cater first and foremost to
endless loop situations.  Its original intent is save me the time it
takes GDB to emit output I don't want to see, plus the time and
nuisance of typing RET while it does.


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