From: Mark Kettenis <kettenis@chello.nl>
To: Richard Henderson <rth@twiddle.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] alpha frame unwind tweakage
Date: Fri, 30 May 2003 18:26:00 -0000 [thread overview]
Message-ID: <867k88cmu2.fsf@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: Richard Henderson's message of "Thu, 29 May 2003 23:44:25 -0700"
Richard Henderson <rth@twiddle.net> writes:
> Two, I was a bit deluded with the hackery surrounding calling
> back into the heuristic unwinder for mdebug frames that were
> still in the prologue. Mainly, if find_proc_desc can find the
> PDR for a function, so can get_pc_function_start. And the
> later works with far more than just mdebug. This seems to
> work slightly better when dealing with executables that don't
> contiain debug info, but do have their symbol table.
>
> Ok?
I'm always in favour of patches that remove code :-), so yes please,
go ahead. However, could you make the loop incremente patch a
seperate commit?
Mark
prev parent reply other threads:[~2003-05-30 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 6:44 Richard Henderson
2003-05-30 18:26 ` Mark Kettenis [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=867k88cmu2.fsf@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=rth@twiddle.net \
/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