From: Kevin Buettner <kevinb@redhat.com>
To: Romain Berrendonner <berrendo@ACT-Europe.FR>
Cc: gdb@sources.redhat.com
Subject: Re: compatibility between gdb and stub
Date: Wed, 27 Nov 2002 11:34:00 -0000 [thread overview]
Message-ID: <1021127193435.ZM31733@localhost.localdomain> (raw)
In-Reply-To: Romain Berrendonner <berrendo@ACT-Europe.FR> "Re: compatibility between gdb and stub" (Nov 21, 10:44am)
On Nov 21, 10:44am, Romain Berrendonner wrote:
> On 2002-11-20, Kevin Buettner wrote :
>
> >
> > As I understand it, if a stub replies with a short "g" packet, then
> > gdb will simply regard the missing registers as being unavailable.
> >
> Let's take the example of the 750, with a stub not aware of fpscr.
>
> They are many registers after fpscr (the first of them is sr0).
> With this scheme, when the stub sends back the answer to a 'g' packet,
> gdb will consider that the content of fpscr is the content of sr0, and that
> thrm3 (the last register) is not available.
This would be true if fpscr was simply added in the middle. However,
when I "added" fpscr, I made it replace a previously unused slot. So,
what should happen in this case is that gdb will simply get a zero (or
some other bogus value) for fpscr.
Kevin
prev parent reply other threads:[~2002-11-27 19:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 6:09 Romain Berrendonner
2002-11-18 8:05 ` Andrew Cagney
2002-11-18 8:46 ` Romain Berrendonner
2002-11-18 14:56 ` Kevin Buettner
2002-11-18 17:40 ` Steven Johnson
2002-11-18 17:43 ` Daniel Jacobowitz
2002-11-19 1:20 ` Romain Berrendonner
2002-11-20 13:04 ` Kevin Buettner
2002-11-20 13:19 ` Andrew Cagney
2002-11-21 1:44 ` Romain Berrendonner
2002-11-26 13:56 ` Andrew Cagney
2002-11-26 15:37 ` Steven Johnson
2002-11-26 16:01 ` Andrew Cagney
2002-11-27 11:34 ` Kevin Buettner [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=1021127193435.ZM31733@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=berrendo@ACT-Europe.FR \
--cc=gdb@sources.redhat.com \
/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