public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: RFC: Two small remote protocol extensions
Date: Wed, 17 Sep 2003 16:19:00 -0000	[thread overview]
Message-ID: <3F688997.4030605@redhat.com> (raw)
In-Reply-To: <20030917155115.GA7896@nevyn.them.org>


> Well, Ht is effectively a new letter - H is only defined for c and g.
> We could explicitly state that, or look for a new letter.  I recommend
> a multi-letter sequence, the extra bytes don't matter and we don't have
> all that many letters.

Definitly a multi-letter sequence, but a new letter :-)

> To summarize, here's what we seem to have now natively:
>   - Single step one thread, all others stopped.
>   - Single step one thread, all others continued.
>   - Signal one thread, all others stopped.
>   - Signal one thread, all others continued.
>   - Continue all threads.
> 
> Here's what I think would be useful, though:
>   - Per thread, specify stopped/singlestepped/signal/continue.
> 
> Some of the combinations aren't useful; singlestepping multiple threads
> for instance is not usually useful.  Well, I suppose it could be.

Who are we to argue :-)

> But specific signals to multiple threads at the same time (well, same
> time is really kind of approximate without better native interfaces...)
> - now that's useful in debugging race conditions.
> 
> So, do you agree?  If so, here's just one possible way to implement it. 
> I left it as Ht because I'm too lazy to go find another letter.  This
> doesn't include step out of range because I'm not sure how that should
> look (what was the problem with step out of range anyway?  That caused
> it to get disabled? - and its current syntax is not in the manual).

It wasn't thread friendly, wasn't documented, it wasn't consistent with 
the other continuation packets (it had two replies).

>   Ht 'TID' 'DISPOSITION' [';' 'TID' 'DISPOSITION']... [';' 'DISPOSITION']
> 
> 'TID' should be a numeric thread ID, to affect one thread.
> 
> 'DISPOSITION' can be:
>   's'
>   'c'
>   'C' 'SIGNAL'

I hope TID is decimal :-)

> A final 'DISPOSITION' is applied to all threads not explicitly listed.
> 
> Note that this Ht is a continue packet, not a select-thread packet.  So
> Ht is not a good choice.

Yep.

Andrew


  reply	other threads:[~2003-09-17 16:19 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-01 19:25 Daniel Jacobowitz
2002-05-02  8:38 ` Andrew Cagney
2002-05-02  8:52   ` Daniel Jacobowitz
2002-05-02  9:39     ` Andrew Cagney
2002-05-02 12:14       ` Daniel Jacobowitz
2002-05-02 12:22         ` Kevin Buettner
2002-05-02 12:34           ` Daniel Jacobowitz
2002-05-02 13:13         ` Andrew Cagney
2002-05-02 14:09           ` Daniel Jacobowitz
2002-05-03 11:24             ` Andrew Cagney
2002-05-03 14:28               ` Daniel Jacobowitz
2002-05-03 15:18                 ` Andrew Cagney
2002-05-03 15:22                   ` Daniel Jacobowitz
2002-05-04 19:59                     ` Andrew Cagney
2002-05-02 13:13   ` Quality Quorum
2002-05-02 14:13     ` Daniel Jacobowitz
2002-05-03 13:07     ` Andrew Cagney
2002-08-16  7:30 ` Daniel Jacobowitz
2002-08-16  7:42   ` Andrew Cagney
2002-08-16  7:52     ` Daniel Jacobowitz
2002-08-16  8:21       ` Andrew Cagney
2002-08-22 19:23       ` Andrew Cagney
2002-08-22 19:36         ` Daniel Jacobowitz
2002-08-23  7:24         ` Quality Quorum
2002-08-23  7:26           ` Daniel Jacobowitz
2002-08-23  7:49             ` Quality Quorum
2002-08-23  8:57           ` Andrew Cagney
2002-08-23 11:16             ` Quality Quorum
2002-08-23 12:39               ` Andrew Cagney
2002-08-23 13:10                 ` Quality Quorum
2002-08-27 20:23                   ` Andrew Cagney
2002-08-28  8:31                     ` Quality Quorum
2002-08-28  9:44                       ` Andrew Cagney
2002-08-28  9:49                         ` Daniel Jacobowitz
2002-08-22 21:08       ` Andrew Cagney
2002-08-23  5:44         ` Daniel Jacobowitz
2002-08-23 12:10           ` Andrew Cagney
2002-08-23 12:53           ` Andrew Cagney
2002-08-23 13:15             ` Daniel Jacobowitz
2002-08-27 21:07               ` Andrew Cagney
2002-08-28  6:33                 ` Daniel Jacobowitz
2002-09-25  8:51                   ` Daniel Jacobowitz
2002-09-25 11:17                     ` Andrew Cagney
2002-09-26 18:39                   ` Andrew Cagney
2002-09-26 18:48                     ` Andrew Cagney
2003-06-29  7:51                     ` Daniel Jacobowitz
2003-09-03 23:41                       ` Andrew Cagney
2003-09-17 15:51                         ` Daniel Jacobowitz
2003-09-17 16:19                           ` Andrew Cagney [this message]
2003-09-17 16:23                             ` Daniel Jacobowitz
2003-09-22  0:27                               ` Andrew Cagney
2003-09-22  1:01                                 ` Daniel Jacobowitz
2003-09-22  3:02                                   ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F688997.4030605@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).