From: Nathan Sidwell <nathan@acm.org>
To: 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, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <c9d53ddc-750a-ec8d-e1e3-7616a83fac5a@acm.org> (raw)
In-Reply-To: <d1d58d83-cf2a-c91d-385b-07afbed26593@redhat.com>
On 06/26/2018 07:39 AM, Florian Weimer wrote:
> On 06/26/2018 01:35 PM, Nathan Sidwell wrote:
>> IIRC, in gcc-land you have to give both noreturn and nothrow
>> attributes to make it non-unwindable.
>
> Are you sure? I was under the impression that GCC did not do this
> because it interferes too much with debugging.
I'm not sure at all. I remember needing to use nothrow somewhere that
throw() didn't cut it, and could well have got the details wrong, and
the compiler has moved on anyway.
> Furthermore, glibc marks abort as nothrow and noreturn, which is a bit
> dubious, considering that it is perfectly fine to throw exception from
> synchronously delivered signals.
Hm, that seems contradictory ...
nathan
--
Nathan Sidwell
next prev parent reply other threads:[~2018-06-26 11:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 Florian Weimer
2018-01-01 0:00 ` Jeff Law
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Jeff Law
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` Jakub Jelinek
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Nathan Sidwell
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Jakub Jelinek
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Nathan Sidwell
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Nathan Sidwell
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Nathan Sidwell [this message]
2018-01-01 0:00 ` Jakub Jelinek
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=c9d53ddc-750a-ec8d-e1e3-7616a83fac5a@acm.org \
--to=nathan@acm.org \
--cc=binutils@sourceware.org \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gnu-gabi@sourceware.org \
--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).