From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-10934-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 25593 invoked by alias); 4 Nov 2002 14:52:19 -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 25574 invoked from network); 4 Nov 2002 14:52:17 -0000
Received: from unknown (HELO mail.alcatel.be) (195.207.101.250)
  by sources.redhat.com with SMTP; 4 Nov 2002 14:52:17 -0000
Received: from alcatel.be (relay3 [127.0.0.1])
	by mail.alcatel.be (8.11.0/8.11.4) with ESMTP id gA4Eige32027;
	Mon, 4 Nov 2002 15:44:42 +0100
Message-ID: <3DC68A0A.7ABED424@alcatel.be>
Date: Mon, 04 Nov 2002 06:52:00 -0000
From: Jan Van Belle <Jan.Van_Belle@alcatel.be>
Organization: Alcatel Telecom
X-Accept-Language: en
MIME-Version: 1.0
To: Daniel Jacobowitz <drow@mvista.com>, gdb@sources.redhat.com
Subject: Re: STEP and CONTINUE in GDB REMOTE
References: <3DC68303.8E34E69B@alcatel.be> <20021104142753.GA12614@nevyn.them.org> <3DC6864D.41D86294@alcatel.be> <20021104144648.GA13511@nevyn.them.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-SW-Source: 2002-11/txt/msg00031.txt.bz2

Daniel Jacobowitz wrote:

> >
> > Yes I have. I have a copy printed out on my desk. This document explains us
> > which possible responses there are,
> > but not when to send which one, and certainly not what the contents should be
> > for
> >
> > TAAn...:r...;n...:r...;n...:r...;
> >
> > I already did several Google's for this topic, but I guess I'll have to find
> > it in someone's private collection
>
> The explanation of T isn't the clearest...
>
> SAA: stop with signal AA
> TAA: stop with signal AA, and return the values of registers that we
>      know will be queried, or other information:
>
> n... = register number (hex), r... = target byte ordered register
> contents, size defined by REGISTER_RAW_SIZE;
>
> n... = `thread', r... = thread process ID, this is a hex integer;
>
> n... = (`watch' | `rwatch' | `awatch', r... = data address, this is a hex integer;
>
> n... = other string not starting with valid hex digit. GDB should ignore this n...,
> r... pair and go on to the next.
>
> NAA is obsolete and Oxx is... frowned upon.
>

Aha, now we're talking
Maybe this could be added in the manual (hint hint)

Thanks a lot !!

Regards,

Jan