Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Correct gdbserver register packets
Date: Sun, 01 Dec 2002 17:14:00 -0000	[thread overview]
Message-ID: <20021202011500.GA19215@nevyn.them.org> (raw)
In-Reply-To: <5.0.2.1.2.20021126162728.02a31e50@ics.u-strasbg.fr>

On Tue, Nov 26, 2002 at 06:27:36PM +0100, Pierre Muller wrote:
>  Currently the cvs sources of gdbserver
> for m68k linux have a problem.
> 
> The problem comes from the fact that the 
> register packet is build from the data in regformats 
> directory. But the m68k cpu file contains two
> registers that are apparently not accessible
> (or at least not fetched by current gdb).
> 
> This causes connection to remote server to 
> stay stucked affect
> that warning.
> reading register 29: Input/output error
> 
> My patch is a liitle bit more genral because I
> read that there are similar problems for other configuration.
> 
> The main idea is to add a new function
> int
> register_present( int regno)
> 
> that by default allways returns one but
> that can be implmented by the target that do
> no supply all the regsiters
> that are in the regformats dir.
> 
> The final patches can be separated probably, but I would first like to 
> get comments on the general direction.

I don't think there's a point yet.  Eventually, once we have a way to
express it properly in the remote protocol, we can handle returning
not-available for registers.  For now all we should need is:

> ChangeLog entry
> 
> 2002-11-26  Pierre Muller  <muller@ics.u-strasbg.fr>
> 
>         * linux-m68k-low.c (m68k_regmap): Add missing  -1.

> Index: 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
> --- linux-m68k-low.c    9 Apr 2002 22:44:43 -0000       1.3
> +++ linux-m68k-low.c    26 Nov 2002 15:26:47 -0000
> @@ -45,24 +45,36 @@ static int m68k_regmap[] =
>  #ifdef PT_FP0
>    PT_FP0 * 4, PT_FP1 * 4, PT_FP2 * 4, PT_FP3 * 4,
>    PT_FP4 * 4, PT_FP5 * 4, PT_FP6 * 4, PT_FP7 * 4,
> -  PT_FPCR * 4, PT_FPSR * 4, PT_FPIAR * 4
> +  PT_FPCR * 4, PT_FPSR * 4, PT_FPIAR * 4,
>  #else
>    21 * 4, 24 * 4, 27 * 4, 30 * 4, 33 * 4, 36 * 4,
> -  39 * 4, 42 * 4, 45 * 4, 46 * 4, 47 * 4
> +  39 * 4, 42 * 4, 45 * 4, 46 * 4, 47 * 4,
>  #endif
> +  -1, -1
>  };
> 

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.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-12-02  1:14 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 [this message]
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

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=20021202011500.GA19215@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=muller@ics.u-strasbg.fr \
    /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