From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: PATCH: use frame_unwind_register instead of frame_register
Date: Mon, 06 Nov 2006 23:27:00 -0000 [thread overview]
Message-ID: <20061106232738.GA20625@nevyn.them.org> (raw)
In-Reply-To: <m3odrknoq6.fsf@codesourcery.com>
On Mon, Nov 06, 2006 at 03:24:01PM -0800, Jim Blandy wrote:
>
> I've committed the below, which 1) uses frame_register_read instead of
> frame_unwind_register, thereby obtaining the registers from the right
> frame, and 2) removes the now-unused variables.
Thanks. We really do need to cut down on the number of functions...
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-11-06 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 22:11 Jim Blandy
2006-11-03 22:23 ` Daniel Jacobowitz
2006-11-06 14:33 ` Daniel Jacobowitz
2006-11-06 20:06 ` Jim Blandy
2006-11-06 23:24 ` Jim Blandy
2006-11-06 23:27 ` 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=20061106232738.GA20625@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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