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: [RFC] 09/10 Add "continue --all"


A Friday 09 May 2008 02:47:20, Daniel Jacobowitz wrote:
> On Fri, May 09, 2008 at 02:36:09AM +0100, Pedro Alves wrote:
> > And after a bit, it hit me that we use /opt most everywhere
> > else, so "continue /a" makes more sense?
>
> I don't know; personally I do not like it.  The other slashed options
> are all output formatting, even Doug's new /m for disassemble.  This
> one is behavior, not option.
>
> Does continue have to handle all threads at once, or is this similar
> to "thread apply all continue"?  

It's basically the same.  I mentioned that upthread.

> We could alias all -> thread apply 
> all.

I love the sound of that!  "all continue".  Perfect.

There's just one difference.  "continue --all" resumes all
threads and prints "Continuing." once, while "all continue" would print
that (or whatever we change it too) once per resuming thread.  That may
actually be better, unless we wanted to compress the output, like

 Continuing all threads
  or
 Continuing thread 2,3,5,7,8,...,20
  vs
 Continuing thread 2
 Continuing thread 3
 Continuing thread 5
 Continuing thread 7
 Continuing thread ...
 Continuing thread 20

But "all continue", "all interrupt", "all ..." seems so perfect that
I'm for all it.

Others?

-- 
Pedro Alves


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