From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
brobecker@adacore.com, jimb@codesourcery.com
Subject: Re: [rfc] Unwind the ARM CPSR
Date: Wed, 17 Oct 2007 06:05:00 -0000 [thread overview]
Message-ID: <20071017010152.GA3534@caradoc.them.org> (raw)
In-Reply-To: <20071017003013.GA31318@caradoc.them.org>
On Tue, Oct 16, 2007 at 08:30:13PM -0400, Daniel Jacobowitz wrote:
> > I think it is a very bad idea. It will take ages before all targets
> > are converted, and having two functions to do the same thing will be
> > even more confusing.
>
> Yes, that's true; it will be confusing. I've taken the opportunity to
> work on a related project at the same time though and so far I like
> the shape of the result:
By the way: if we do make this switch, I will personally commit to
fixing every single unwinder in GDB before the next release and
eliminating all traces of the current prev_register method.
I sure hope someone appreciates that offer enough to help. I think
I'm out of my mind. There are 68 of them in the source tree now and
they have tendrils all over the place. But I did my share of shouting
about how much of GDB was deprecated and then left to rot; I do not
want to contribute to the problem.
I'm not volunteering to test all of them, but I'll test the ones
I can and make mechanical fixes to the rest.
Fortunately about half of those use trad-frame.c.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-17 1:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 14:59 Daniel Jacobowitz
2007-10-11 15:52 ` Daniel Jacobowitz
2007-10-12 8:08 ` Joel Brobecker
2007-10-16 22:09 ` Mark Kettenis
2007-10-17 0:36 ` Daniel Jacobowitz
2007-10-17 6:05 ` Daniel Jacobowitz [this message]
2007-10-17 13:18 ` Joel Brobecker
2007-10-19 11:54 ` Ulrich Weigand
2007-10-17 0:30 ` Mark Kettenis
2008-05-01 18:31 ` Daniel Jacobowitz
2008-05-01 18:35 ` Daniel Jacobowitz
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=20071017010152.GA3534@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=mark.kettenis@xs4all.nl \
/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