Re: Translate signal to C++ exception

[christos%astron.com@localhost (Christos Zoulas)]

In article <20160409205106.GA12732%britannica.bec.de@localhost>,
Joerg Sonnenberger  <joerg%britannica.bec.de@localhost> wrote:
>On Sat, Apr 09, 2016 at 11:05:33AM -0400, Christos Zoulas wrote:
>> On Apr 9,  4:11am, n54%gmx.com@localhost (Kamil Rytarowski) wrote:
>> -- Subject: Re: Translate signal to C++ exception
>> 
>> | How to do proper unwinding?
>> | 
>> | I was trying to disable custom signal stack with sigaltstack(2) but
>> | always I got backtrace(3) without history beyond signal trampoline.
>> | 
>> | I don't know how to go beyond the trampoline.
>> 
>> The only way is through proper cfi annotations, and even then it is
>> doubtful it will work.
>
>Are we talking about sync or async signals? For sync signals, it is no
>big issue. Async signals are a whole lot different and sigaltstack is
>difficult to avoid for them.

For both... For traps (sync) it can probably work; for other signals
it probably will not.

christos