From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Work around ARM RV compiler unwind info
Date: Thu, 04 Jan 2007 20:25:00 -0000 [thread overview]
Message-ID: <20070104202545.GD24634@nevyn.them.org> (raw)
In-Reply-To: <m3odpz7hgs.fsf@codesourcery.com>
On Tue, Dec 19, 2006 at 12:34:27PM -0800, Jim Blandy wrote:
> It's hard for me to guess how much benefit these will provide to
> users, but it seems like the burden this patch places on GDB
> developers is pretty minor; given the task, I think it's pretty clean.
> Since we want to grow GDB's user base, I'm in favor of this patch.
And no other comments, so that's good enough for me; I retested and
checked it in.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-01-04 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 21:59 Daniel Jacobowitz
2006-12-19 20:33 ` Jim Blandy
2007-01-04 20:25 ` 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=20070104202545.GD24634@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