Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: The ari hits
Date: Sun, 02 Mar 2003 03:14:00 -0000	[thread overview]
Message-ID: <20030302031453.GA13768@nevyn.them.org> (raw)
In-Reply-To: <3E616656.5020500@redhat.com>

On Sat, Mar 01, 2003 at 09:03:02PM -0500, Andrew Cagney wrote:
> 
> >>	REGISTER_VIRTUAL_SIZE (...) /* OK */
> >>
> >>(the ``/* OK */'' gags the ARI) and add a comment.
> >>
> >>sorry about this,
> >
> >
> >That makes a lot more sense now, thank you!  I just assumed you were
> >implying the gdbarch_ prefix.
> >
> >Here's another question, though.  frame_register may return a cooked
> >value, but frame_saved_regs_register_unwind uses a buffer of
> >REGISTER_RAW_SIZE.  Is using REGISTER_VIRTUAL_SIZE in core code really
> >safe?
> 
> Hmm, no, sorry.  It's the value_of_register() value_from_register() code 
> that plays with virtual_size, not frame_register() et.al.
> 
> On the bright side, this means that it can use register_size() as that, 
> when given a choice, should return the raw size.

Thanks, that makes sense.  I'll fix up the patch and commit tomorrow.

By the way, in register_size():
  gdb_assert (size == REGISTER_RAW_SIZE (regnum)); /* OK */
  gdb_assert (size == REGISTER_RAW_SIZE (regnum)); /* OK */

They're both OK, but I suspect one of them is wrong anyway :)

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-03-02  3:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 22:07 Andrew Cagney
2003-02-28  1:52 ` Daniel Jacobowitz
2003-02-28 17:54   ` Andrew Cagney
2003-02-28 17:59     ` Daniel Jacobowitz
2003-03-02  2:01       ` Andrew Cagney
2003-03-02  3:14         ` Daniel Jacobowitz [this message]
2003-03-03 21:49           ` Daniel Jacobowitz
2003-10-10  2:52 The ARI hits Andrew Cagney

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=20030302031453.GA13768@nevyn.them.org \
    --to=drow@mvista.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