From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9966 invoked by alias); 4 Nov 2002 14:59:44 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9903 invoked from network); 4 Nov 2002 14:59:43 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 4 Nov 2002 14:59:43 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id DF01C3E18; Mon, 4 Nov 2002 09:59:42 -0500 (EST) Message-ID: <3DC68B5E.3080502@redhat.com> Date: Mon, 04 Nov 2002 06:59:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Jan Van Belle , 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; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-11/txt/msg00033.txt.bz2 > 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. Why not do the reply in texinfo? That way it can be dropped into the manual :-) Andrew