From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-15596-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 25240 invoked by alias); 22 Sep 2003 00:27:32 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 25231 invoked from network); 22 Sep 2003 00:27:32 -0000
Received: from unknown (HELO localhost.redhat.com) (207.219.125.105)
  by sources.redhat.com with SMTP; 22 Sep 2003 00:27:32 -0000
Received: from redhat.com (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 4713C2B89; Sun, 21 Sep 2003 20:27:32 -0400 (EDT)
Message-ID: <3F6E41F4.2090603@redhat.com>
Date: Mon, 22 Sep 2003 00:27:00 -0000
From: Andrew Cagney <ac131313@redhat.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: RFC: Two small remote protocol extensions
References: <20020823124453.GA12257@nevyn.them.org> <3D6692AE.90601@ges.redhat.com> <20020823201549.GB26809@nevyn.them.org> <3D6C4C4E.4050409@ges.redhat.com> <20020828133445.GA16642@nevyn.them.org> <3D93B6E6.8030805@redhat.com> <20030629021605.GA18990@nevyn.them.org> <3F567C28.1040906@redhat.com> <20030917155115.GA7896@nevyn.them.org> <3F688997.4030605@redhat.com> <20030917162321.GA25144@nevyn.them.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-09/txt/msg00259.txt.bz2


> OK.  I think there's room to add it to something like this, so I'm not
> gonna fret about it for now.
> 
> 
>> >  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 :-)

Hmm, I think it should be more LL1, which the above (and the remote 
protocol :-) isn't.  Something like:

c:TID
s:TID
C:SIG:TID

that way someone can later add:

p:REG:VALUE

Oh and TID is hex:

      if (strncmp (p, "thread", p1 - p) == 0)
        {
          p_temp = unpack_varlen_hex (++p1, &thread_num);

 > by @code{REGISTER_RAW_SIZE}; @var{n...} = @samp{thread}, @var{r...} =
 > thread process ID, this is a hex integer; @var{n...} = (@samp{watch} |

:-(

> Heh, 'c', right.  Any objection to using decimal thread IDs, or would
> you rather have 'TID' : 'DISPOSITION' ; ... ?
> 
> 
>> >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.
> 
> 
> How about, um, "vCont"?

As in:

	vCont;s:456;C04:aba;c

or "n" for "next"

	[n]ext;s:456;C04:aba;c

Main thing is that, the entire leading word must be matched.

The choice, I think, is: a, e, E, f, h, j, J, K, l, L, n, N, o, O, u, U, 
v, V, w, x, y, Y.

(I should mark [eE] has do-not-use).

Andrew