From: Steven Johnson <sjohnson@neurizon.net>
To: gdb@sources.redhat.com
Subject: Re: compatibility between gdb and stub
Date: Tue, 26 Nov 2002 15:37:00 -0000 [thread overview]
Message-ID: <3DE40436.4060102@neurizon.net> (raw)
In-Reply-To: <3DE3EE0E.4010009@redhat.com>
The real problem here is that the Common Registers of PowerPC are not
uniform across the chips. I think the only ones that can truly be said
to be common are R0-R31,pc,msr,lr,ctr,flags The macros defined, assume
a whole lot about what is common, that isn't.
And having written an "old stub" for the MPC860, I can confidently say
that old stubs did not supply zeros where fpscr is, they didn't send
anything as GDB did not expect anything.
Obviously there would need to be some understanding in the stub of what
registers GDB used, but I fail to see that GDB is ever going to
permenantly define a packet layout and stick to it.
Steven
>
> No. An old stub would supply zeros instead of "fpscr".
>
>> This is clumsy, but the 'qRegisters' packet should improve this
>> behaviour :-)
>
>
> qRegisters isn't a `silver bullet' :-/ The bottom line is that GDB and
> the stub need to agree to a packet layout and then stick to it.
>
> Andrew
>
>
>
next prev parent reply other threads:[~2002-11-26 23:37 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 [this message]
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=3DE40436.4060102@neurizon.net \
--to=sjohnson@neurizon.net \
--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