Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Richard.Earnshaw@arm.com
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb@sources.redhat.com
Subject: Re: REGISTER_BYTE() and pseudos
Date: Wed, 15 May 2002 13:01:00 -0000	[thread overview]
Message-ID: <3CE2BEA4.6050809@cygnus.com> (raw)
In-Reply-To: <200205151807.TAA18580@cam-mail2.cambridge.arm.com>

> OK, I see what you are doing.  Basically, if a pseudo maps onto a real 
> register somewhere in the regcache, you return the address of that.
> 
> However, what should be done if the pseudo doesn't exist as a single 
> entry, or if it is a manipulation of a real register?  For example, on the 
> ARM, the CPSR may be just a few bits retrieved from the PC.
> 
> Also, what would you do if you needed to address two non-adjacent 
> registers?

Return ``not_lval''.  I think that case can go in the too hard basket.

First, I don't know if GDB's ``struct value'' system is rich enough to 
describe a value split across [disjoint] registers and memory.  Second, 
even if it was, the current get_saved_register() doesn't make that 
knowledge available.  An interface more like value_of_register() would 
be better.

BTW, this code:

 > OK, I'll have another look.
 >
 > The bit I'm worried about though is if we call something like
 > generic_get_saved_register for a pseudo and we hit a call_dummy frame.
 > The code in there goes:
 >
 >       if (PC_IN_CALL_DUMMY (frame->pc, frame->frame, frame->frame))
 >         {
 >           if (lval)             /* found it in a CALL_DUMMY frame */
 >             *lval = not_lval;
 >           if (raw_buffer)
 >             memcpy (raw_buffer,
 >                     generic_find_dummy_frame (frame->pc, frame->frame) +
 >                     REGISTER_BYTE (regnum),
 >                     REGISTER_RAW_SIZE (regnum));
 >           return;
 >
 > Which will try to look up the pseudo in the buffer even if it isn't 
there.


Reveals a problem with the patch:
http://sources.redhat.com/ml/gdb-patches/2002-05/msg00416.html

For the moment a custom get_saved_register will get around this.


Andrew


      parent reply	other threads:[~2002-05-15 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15  9:36 Richard Earnshaw
2002-05-15 10:06 ` Andrew Cagney
2002-05-15 10:35   ` Elena Zannoni
2002-05-15 10:46     ` Richard Earnshaw
2002-05-15 11:46       ` Elena Zannoni
2002-05-15 11:08     ` Richard Earnshaw
2002-05-15 11:45       ` Elena Zannoni
2002-05-15 13:01       ` Andrew Cagney [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=3CE2BEA4.6050809@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=ezannoni@redhat.com \
    --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