Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: Andreas Schwab <schwab@suse.de>, gdb-patches@sources.redhat.com
Subject: Re: [RFC] Correct gdbserver register packets
Date: Mon, 02 Dec 2002 06:57:00 -0000	[thread overview]
Message-ID: <20021202145755.GA8503@nevyn.them.org> (raw)
In-Reply-To: <5.0.2.1.2.20021202151721.02ad5008@ics.u-strasbg.fr>

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 <drow@mvista.com> 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


  reply	other threads:[~2002-12-02 14:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26  9:29 Pierre Muller
2002-12-01 17:14 ` Daniel Jacobowitz
2002-12-02  2:44   ` Andreas Schwab
2002-12-02  6:14     ` Daniel Jacobowitz
2002-12-02  6:22       ` Pierre Muller
2002-12-02  6:57         ` Daniel Jacobowitz [this message]
2002-12-02 21:20     ` Daniel Jacobowitz
2002-12-03  0:31       ` Pierre Muller
2002-12-03 19:55         ` Daniel Jacobowitz
2002-12-04  4:28           ` Andreas Schwab
2003-01-04 21:56           ` Daniel Jacobowitz

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=20021202145755.GA8503@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=muller@cerbere.u-strasbg.fr \
    --cc=schwab@suse.de \
    /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