From: Andreas Schwab <schwab@suse.de>
To: Josef Wolf <jw@raven.inka.de>
Cc: gdb@sources.redhat.com
Subject: Re: Need Help for bringing m68k-based bdm target-patches form gdb-5.2.1 to gdb-5.3
Date: Wed, 06 Aug 2003 18:22:00 -0000 [thread overview]
Message-ID: <jed6fisl1z.fsf@sykes.suse.de> (raw)
In-Reply-To: <20030731223514.GD20282@raven.inka.de> (Josef Wolf's message of "Fri, 1 Aug 2003 00:35:14 +0200")
Josef Wolf <jw@raven.inka.de> writes:
|> diff -urd gdb/gdb/m68k-tdep.c gdb.patched/gdb/m68k-tdep.c
|> --- gdb/gdb/m68k-tdep.c 2003-07-31 18:15:46.000 +0200
|> +++ gdb.patched/gdb/m68k-tdep.c 2003-07-31 18:21:56.00 +0200
|> @@ -60,14 +60,14 @@
|> E_SP_REGNUM = 15, /* Contains address of top of stack */
|> E_PS_REGNUM = 16, /* Contains processor status */
|> E_PC_REGNUM = 17, /* Contains program counter */
|> - E_FP0_REGNUM = 18, /* Floating point register 0 */
|> + E_FP0_REGNUM = 26, /* Floating point register 0 */
|> E_FPC_REGNUM = 26, /* 68881 control register */
There are 7 registers between fp0 and fpc, namely the other floating point
registers fp1 to fp7. You can't just renumber fp0 without renumbering the
others.
|> That is, there are two problems. First is that the bdm-enabled target have
|> some additional registers. Those registers are
|>
|> "pcc", "usp", "ssp", "sfc", "dfc", "atemp", "far", "vbr",
|>
|> which are placed between "pc" and "fp0". Most of those registers are
|> standard m68k registers,
But they are supervisor-only registers (btw, I have never heard of the
pcc, atemp and far registers, they don't exist on any of the variants of
the m68k family I know of).
|> so I wonder how E_FP0_REGNUM can be set to 18?
Theses numbers are basically arbitrary, AFAIK.
|> Could it be that the bdm-patches have a broken register mapping? Or is
|> it that gdb dont want to know anything about vbr, ssp, sfc etc/pp?
The latter. No user level program can ever use these registers, so gdb
does not need to know anything about them. But if you want gdb to be
able to debug supervisor level programs you can just give these registers
any number beyond the currently defined range.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-08-06 18:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 22:36 Josef Wolf
2003-08-05 21:50 ` Josef Wolf
2003-08-06 16:09 ` Andrew Cagney
2003-08-06 22:17 ` Josef Wolf
2003-08-09 14:31 ` Andrew Cagney
2003-08-10 21:16 ` Josef Wolf
2003-08-06 18:22 ` Andreas Schwab [this message]
2003-08-06 20:55 ` Josef Wolf
2003-08-07 6:08 ` Andreas Schwab
2003-08-07 14:35 ` Andrew Cagney
2003-08-10 20:59 ` Josef Wolf
2003-08-10 20:48 ` Josef Wolf
2003-08-11 9:36 ` Andreas Schwab
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=jed6fisl1z.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb@sources.redhat.com \
--cc=jw@raven.inka.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).