Invalid program counters and unwinding

[Nathan Sidwell]

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