Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Cc: Pierre Muller <muller@cerbere.u-strasbg.fr>,
	Andreas Schwab <schwab@suse.de>
Subject: Re: [RFC] Correct gdbserver register packets
Date: Sat, 04 Jan 2003 21:56:00 -0000	[thread overview]
Message-ID: <20030104215651.GB28756@nevyn.them.org> (raw)
In-Reply-To: <20021204035534.GA16186@nevyn.them.org>

On Tue, Dec 03, 2002 at 10:55:34PM -0500, Daniel Jacobowitz wrote:
> On Tue, Dec 03, 2002 at 09:29:14AM +0100, Pierre Muller wrote:
> > At 06:21 03/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.
> > >
> > >There's a much easier solution: change the 31 to 29, and remove the
> > >extra two registers from regformats/.  I'm not familiar with any m68k
> > >stubs; do you know of any others that do or do not include the extra
> > >two registers, which GDB no longer seems to know anything about?  Or
> > >are they just bogus?
> > 
> > 
> > config/m68k/tm-sun3.h 
> > seems to use 31 registers including the two not known by
> > other m68k targets...
> > But I don't known the state of that target...
> 
> "very old".  It seems that the base for all/most m68k targets is to
> have 29 registers.  As a result, I think this patch is the way to go. 
> Could you two give it a try?

Since this worked for Andreas, I've checked it in.  With appropriate
copyright date updates this time.

> 2002-11-30  Andreas Schwab  <schwab@suse.de>
> 
> 	* linux-m68k-low.c (m68k_num_regs): Define to 29 instead of 31.
> 
> 2002-12-03  Daniel Jacobowitz  <drow@mvista.com>
> 
> 	* regformats/reg-m68k.dat: Remove fpcode and fpflags.
> 
> Index: gdbserver/linux-m68k-low.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/gdbserver/linux-m68k-low.c,v
> retrieving revision 1.3
> diff -u -p -r1.3 linux-m68k-low.c
> --- gdbserver/linux-m68k-low.c	9 Apr 2002 22:44:43 -0000	1.3
> +++ gdbserver/linux-m68k-low.c	4 Dec 2002 03:43:52 -0000
> @@ -26,7 +26,7 @@
>  #include <sys/reg.h>
>  #endif
>  
> -#define m68k_num_regs 31
> +#define m68k_num_regs 29
>  
>  /* This table must line up with REGISTER_NAMES in tm-m68k.h */
>  static int m68k_regmap[] =
> Index: regformats/reg-m68k.dat
> ===================================================================
> RCS file: /cvs/src/src/gdb/regformats/reg-m68k.dat,v
> retrieving revision 1.1
> diff -u -p -r1.1 reg-m68k.dat
> --- regformats/reg-m68k.dat	1 Feb 2002 22:05:28 -0000	1.1
> +++ regformats/reg-m68k.dat	4 Dec 2002 03:43:52 -0000
> @@ -31,5 +31,3 @@ expedite:sp,fp,pc
>  32:fpcontrol
>  32:fpstatus
>  32:fpiaddr
> -32:fpcode
> -32:fpflags
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      parent reply	other threads:[~2003-01-04 21:56 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
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 [this message]

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=20030104215651.GB28756@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