From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26569 invoked by alias); 2 Dec 2002 14:57:33 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 26561 invoked from network); 2 Dec 2002 14:57:32 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 2 Dec 2002 14:57:32 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18IttK-000349-00; Mon, 02 Dec 2002 10:57:54 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18Is1D-0002Ds-00; Mon, 02 Dec 2002 09:57:55 -0500 Date: Mon, 02 Dec 2002 06:57:00 -0000 From: Daniel Jacobowitz To: Pierre Muller Cc: Andreas Schwab , gdb-patches@sources.redhat.com Subject: Re: [RFC] Correct gdbserver register packets Message-ID: <20021202145755.GA8503@nevyn.them.org> Mail-Followup-To: Pierre Muller , Andreas Schwab , gdb-patches@sources.redhat.com References: <5.0.2.1.2.20021126162728.02a31e50@ics.u-strasbg.fr> <20021202011500.GA19215@nevyn.them.org> <5.0.2.1.2.20021202151721.02ad5008@ics.u-strasbg.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.0.2.1.2.20021202151721.02ad5008@ics.u-strasbg.fr> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-12/txt/msg00019.txt.bz2 On Mon, Dec 02, 2002 at 03:20:39PM +0100, Pierre Muller wrote: > At 15:15 02/12/2002, Daniel Jacobowitz wrote: > >On Mon, Dec 02, 2002 at 11:44:31AM +0100, Andreas Schwab wrote: > >> Daniel Jacobowitz writes: > >> > >> |> Or else Andreas's patch to decrease the number of registers. Hmm, > >> |> probably doing it Andreas's way is better. I'll take care of this in > >> |> the morning. > >> > >> My way of fixing it is not complete, I get "Wrong sized register packet" > >> messages from gdbserver. > > > >Really? Oh, I suppose that gdbserver is receiving 31 registers back > >from GDB. > > > >Why is that happening? There are 31 registers in m68k_register_name > >but no remaining target implements the last two (did any obsolete > >target?) and the register packet appears to be sized for 29 registers. > > > >I'll investigate. > > > See regformats directory! > reg-m68k.dat define 31 > fpcode and fpflags are not known to linux, but I don't know > for other targets... No, only gdbserver uses the data in regformats/. The question is why the GDB _client_ is sending more than 29 registers. I can't see why. > Maybe we should add a new packet that would > give out the name and the format of all the registers that are sent > in the register packet. > This would be sent by the remote GDB program at > connexion and gdbserver would then > and use the result of that first packet > to check which register he connected GDB wants, > if we know them and if the format is correct. Search the archives for qRegisters... -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer