From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org, Mark Kettenis <kettenis@gnu.org>,
Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [RFC] Using values to handle unwinding
Date: Sat, 05 Apr 2008 15:56:00 -0000 [thread overview]
Message-ID: <20080404175316.GA31744@caradoc.them.org> (raw)
In-Reply-To: <20080404173710.GE24753@adacore.com>
Thanks for looking at them!
On Fri, Apr 04, 2008 at 10:37:10AM -0700, Joel Brobecker wrote:
> > I'd love comments on the patches, the overall approach, and how to
> > proceed. Ideally, we check this in (breaking many targets), update
> > each target completely as someone needs that target, and make sure all
> > targets are updated by the next release of GDB. I personally use
> > amd64, i386, arm, mips, m68k, and powerpc; so I'm pretty likely to
> > update all of those (mechanically). I'll do the laggards before the
> > next release too, but not right this minute. I would appreciate
> > assistance with other targets :-)
>
> You said "mechanically" - does it mean you are not able to test some
> of the targets you listed?
I can test a representative triplet. But there's a wide variety of OS
tdep files with sniffers; the patches I've already posted change about
a dozen targets, only one of which I can readily test. So a certain
amount of mechanical conversion and proofreading is the best I can
do.
> We can use a second pair of eyes as our means of testing...
Yes indeed :-)
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-04-04 17:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 16:04 Daniel Jacobowitz
2007-10-17 22:09 ` Daniel Jacobowitz
2007-10-19 11:42 ` Ulrich Weigand
2007-10-19 11:49 ` Daniel Jacobowitz
2007-10-19 4:30 ` Joel Brobecker
2007-10-19 11:43 ` Daniel Jacobowitz
2007-10-19 12:10 ` Ulrich Weigand
2007-10-19 12:40 ` Daniel Jacobowitz
2008-03-31 23:41 ` Daniel Jacobowitz
2008-04-04 17:53 ` Joel Brobecker
2008-04-05 15:56 ` 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=20080404175316.GA31744@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=kettenis@gnu.org \
--cc=uweigand@de.ibm.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