From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Cc: Andrew Cagney <ac131313@redhat.com>, Fred Fish <fnf@intrinsity.com>
Subject: Re: [RFA] Testing REGISTER_NAME in mips-linux-nat.c
Date: Mon, 07 Jul 2003 18:09:00 -0000 [thread overview]
Message-ID: <20030707151834.GB6349@nevyn.them.org> (raw)
In-Reply-To: <20030628183631.GA25309@nevyn.them.org>
On Sat, Jun 28, 2003 at 02:36:31PM -0400, Daniel Jacobowitz wrote:
> On Fri, Jun 27, 2003 at 03:31:18PM -0400, Andrew Cagney wrote:
> > >A recent change to mips_register_name to return a empty string for
> > >register numbers < NUM_REGS is causing problems with the native mips
> > >linux port. The change in mips_register_name is:
> >
> > Arrgh, they keep turning up :-(
> >
> > > + /* Map [NUM_REGS .. 2*NUM_REGS) onto the raw registers, but then
> > > + don't make the raw register names visible. */
> > > + int rawnum = regno % NUM_REGS;
> > > + if (regno < NUM_REGS)
> > > + return "";
> > >
> > >Now for example when mips_linux_cannot_fetch_register() is called with
> > >regno == PC_REGNUM, it will return 1 and reading of the PC will return
> > >zero as the PC value.
> > >
> > >I think this is the correct patch, but I'm not 100% sure. Perhaps we
> > >can just eliminate the REGISTER_NAME check completely.
> >
> > The assertion:
> >
> > gdb_assert (regno >= 0 && regno < NUM_REGS);
> >
> > holds so, yes, eliminating REGISTER_NAME would make sense.
>
> Take a look at MIPS_REGISTER_NAMES in tm-mips.h, which is the generic
> registers. Note lots of empty (unnamed) entries in there - we can't
> fetch or store those. That's what the check is trying to avoid.
>
> I don't think Fred's patch is right either, because this function
> shouldn't even be called for regno > NUM_REGS, so it just disables the
> check. I think the right thing to do is either (ugh!) to call
> REGISTER_NAME (regno + NUM_REGS), or to switch to an inclusive list of
> available registers. Which is easier, and cleaner.
>
> Fred, my mips-linux box is offline at the moment, so I can't test this.
> Could you try the attached patch and let me know if it works?
>
> I think I'm going to try to get my own breed of automated testing
> going to cover this...
>
> > Hmm, how come this doesn't just use PTRACE_GETREGS?
>
> Because mips-linux doesn't implement that yet.
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
>
> 2003-06-28 Daniel Jacobowitz <drow@mvista.com>
>
> * mips-linux-nat.c (mips_linux_cannot_fetch_register)
> (mips_linux_cannot_store_register): List supported instead of
> unsupported registers.
I've checked this in everywhere.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-07-07 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 17:20 Fred Fish
2003-06-27 19:31 ` Andrew Cagney
2003-06-28 18:36 ` Daniel Jacobowitz
2003-07-03 0:44 ` Fred Fish
2003-07-07 18:09 ` Daniel Jacobowitz [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=20030707151834.GB6349@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=fnf@intrinsity.com \
--cc=gdb-patches@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