From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/mips(commit?)] Unwinding from noreturn function
Date: Wed, 07 Mar 2007 12:20:00 -0000 [thread overview]
Message-ID: <20070307122032.GB18998@caradoc.them.org> (raw)
In-Reply-To: <20070307041643.GJ25742@adacore.com>
On Tue, Mar 06, 2007 at 08:16:43PM -0800, Joel Brobecker wrote:
> However, this doesn't work very well in our case, especially
> in this situation:
>
> static const struct frame_unwind *
> mips_insn16_frame_sniffer (struct frame_info *next_frame)
> {
> CORE_ADDR pc = frame_unwind_address_in_block (next_frame, NORMAL_FRAME);
> if (mips_pc_is_mips16 (pc))
> return &mips_insn16_frame_unwind;
> return NULL;
> }
I Am Dumb. Check CVS history, but I think I changed that just a
couple of weeks ago; I audited all the sniffers looking for what ought
to use the unwound PC and what ought to use the unwound block address.
Here, I'm pretty sure I made the wrong choice.
I would recommend you revert my changes to this function and
mips_insn32_frame_sniffer instead.
> It seems to me that the above check is only an optimization,
> and I've spotted at least one instance where I cannot see an
> obvious guaranty that the address has not been decremented
> by one of the _in_block functions... So the decision I made
> was to remove that check.
No, it's not just an optimization. Especially with limited debug
info, it's important.
>
> 2. One minor: There was a confusion in the unwinder between
> the return address and the address of the instruction calling us.
> So I replaced frame_pc_unwind calls by their associated
> frame_unwind_address_in_block.
This half looks right.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-07 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 4:16 Joel Brobecker
2007-03-07 12:20 ` Daniel Jacobowitz [this message]
2007-03-07 21:42 ` Joel Brobecker
2007-03-07 21:44 ` 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=20070307122032.GB18998@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--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