From: Romain Berrendonner <berrendo@ACT-Europe.FR>
To: gdb@sources.redhat.com
Subject: compatibility between gdb and stub
Date: Mon, 18 Nov 2002 06:09:00 -0000 [thread overview]
Message-ID: <20021118140945.GF1252@torino.act-europe.fr> (raw)
Hi folks,
I would like to know what is the policy regarding the compatibility
between gdb and the target stubs: as far as I understand, the way `g'
and 'G' commands work requires that the debugger and the stub have the
very same definition of the target's registers.
The file rs6000-tdep.c however, which was very similar in gdb 5.1 and
gdb 5.2, changed in the 5.3 branch, causing interoperability disruption
with older stubs, due to the definition of fpscr.
Is this correct ? Is there a policy for handling that kind of issues ?
--
Romain
next reply other threads:[~2002-11-18 14:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 6:09 Romain Berrendonner [this message]
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
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=20021118140945.GF1252@torino.act-europe.fr \
--to=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