From: Michael Matz <matz@suse.de>
To: Jeff Law <law@redhat.com>
Cc: Florian Weimer <fweimer@redhat.com>, GCC <gcc@gcc.gnu.org>,
GNU C Library <libc-alpha@sourceware.org>,
Binutils <binutils@sourceware.org>,
gnu-gabi@sourceware.org
Subject: Re: Invalid program counters and unwinding
Date: Mon, 02 Jul 2018 15:48:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1807021743390.15410@wotan.suse.de> (raw)
In-Reply-To: <6c555c05-e6d7-f37a-577f-4e0559c36f76@redhat.com>
Hi,
On Thu, 28 Jun 2018, Jeff Law wrote:
> I believe "dumb" is referring to the fact that we're already in a bit of
> a weird state as evidenced by the NULL FDE. Blindly trying to read the
> contents of the PC that we couldn't map to an FDE is, IMHO, dumb.
>
> One might even be able to argue in this day and age that we should have
> suitable descriptors for everything. If no suitable descriptor is found
> then backtracing should stop. Lack of suitable descriptors in any code
> would be considered a bug in that scenario.
I disagree. ASM code often lacks unwind descriptors (now less than in the
past, but still). My rule of thumb is always: no descriptor -> has to be
a framepointer-using routine with standard calling sequence. (I.e.
declare the combination of no descriptor and no fp to be a bug). Some of
the callee-saved register will temporarily be wrong but unwinding can
continue.
Ciao,
Michael.
next prev parent reply other threads:[~2018-07-02 15:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 9:26 Florian Weimer
2018-06-26 10:56 ` Nathan Sidwell
2018-06-26 11:01 ` Florian Weimer
2018-06-26 11:15 ` Nathan Sidwell
2018-06-26 11:21 ` Florian Weimer
2018-06-26 11:35 ` Nathan Sidwell
2018-06-26 11:39 ` Florian Weimer
2018-06-26 11:46 ` Jakub Jelinek
2018-06-26 11:46 ` Nathan Sidwell
2018-06-26 11:25 ` Jakub Jelinek
2018-06-26 11:31 ` Florian Weimer
2018-06-28 2:16 ` Jeff Law
2018-06-28 12:31 ` Florian Weimer
2018-06-28 14:18 ` Jeff Law
2018-06-28 14:49 ` Florian Weimer
2018-07-02 15:48 ` Michael Matz [this message]
2018-07-02 15:54 ` Jakub Jelinek
2018-07-02 16:14 ` Michael Matz
2018-07-05 19:31 ` Florian Weimer
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=alpine.LSU.2.21.1807021743390.15410@wotan.suse.de \
--to=matz@suse.de \
--cc=binutils@sourceware.org \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gnu-gabi@sourceware.org \
--cc=law@redhat.com \
--cc=libc-alpha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).