From: David Carlton <carlton@math.stanford.edu>
To: Keith Seitz <keiths@redhat.com>
Cc: "gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>,
Andrew Cagney <ac131313@redhat.com>
Subject: Re: [rfa] missing frame_register
Date: Mon, 17 Mar 2003 21:05:00 -0000 [thread overview]
Message-ID: <ro1hea1emaf.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <1047935045.1490.50.camel@lindt.uglyboxes.com>
On 17 Mar 2003 13:04:05 -0800, Keith Seitz <keiths@redhat.com> said:
> On Mon, 2003-03-17 at 11:47, David Carlton wrote:
> I was hoping not to have to do anything about this until later (let 'em
> sweat for a few hours! :v), but I don't believe the below will work:
>> + frame_register (deprecated_selected_frame, regnum, &optim,
>> + NULL, NULL, &realnum, raw_buffer);
> In frame.c:
> void
> frame_register (struct frame_info *frame, int regnum,
> int *optimizedp, enum lval_type *lvalp,
> CORE_ADDR *addrp, int *realnump, void *bufferp)
> {
> /* Require all but BUFFERP to be valid. A NULL BUFFERP indicates
> that the value proper does not need to be fetched. */
> gdb_assert (optimizedp != NULL);
> gdb_assert (lvalp != NULL);
> gdb_assert (addrp != NULL);
> gdb_assert (realnump != NULL);
> /* gdb_assert (bufferp != NULL); */
Oh. Whoops. I guess I could have done a bit more checking! I guess
I needed a few more dummy variables, or something.
> I have a patch that does work (I think), and I will check it in
> momentarily, unless you want to follow through.
Thanks, be my guest.
> I appreciate your thinking of me, urgh, insight!
Well, I figured I owed insight one after I inadvertently broke it
twice a month or so back.
David Carlton
carlton@math.stanford.edu
prev parent reply other threads:[~2003-03-17 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 19:47 David Carlton
2003-03-17 20:56 ` Keith Seitz
2003-03-17 21:05 ` David Carlton [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=ro1hea1emaf.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@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