From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit/mips] frame conversion, pass #1
Date: Mon, 09 Feb 2004 16:24:00 -0000 [thread overview]
Message-ID: <4027B43A.30209@gnu.org> (raw)
In-Reply-To: <20040209060206.GA14162@nevyn.them.org>
> On Mon, Feb 09, 2004 at 12:42:51AM -0500, Andrew Cagney wrote:
>
>> Hello,
>>
>> This is is the first pass of converting the MIPS to the new frame code.
>> This pass gets the MIPS using the new framework (but with a hybrid
>> heuristic + proc_desc unwinder). Later passes will gut much of the now
>> dead code, and split things into two unwinders. I've committed it now
>> cos the 64-bit results are sooo much better (like it works) - not bad
>> for an afternoon hack.
>>
>> Note that it still lacks sigtramp unwinders.
>
>
> I'll be delighted to fix that (for linux at least) - I've got local
> ones, but the way I integrated them with the existing IRIX (?) sigtramp
> code was so unspeakably gross that I decided to wait until the new
> frame code was ready :)
Yes.
Andrew
prev parent reply other threads:[~2004-02-09 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 5:43 Andrew Cagney
2004-02-09 6:02 ` Daniel Jacobowitz
2004-02-09 16:24 ` Andrew Cagney [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=4027B43A.30209@gnu.org \
--to=cagney@gnu.org \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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