Re: Translate signal to C++ exception

[Kamil Rytarowski <n54%gmx.com@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09.04.2016 22:51, Joerg Sonnenberger 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.
> 

SIGSEGV from the code, I assume it's synchronous one from the program
point of view.

All other ones (like from kill(1)) can and should be filtered out.

> Joerg
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXCW7vAAoJEEuzCOmwLnZspSAQAIdcVqmgHYCJoKPMky4sJ+6d
Amljgye5byXo5aogYNZDhAN99wrdQV7N8I+q+StGNkb7A+BJKfERPWdz2K/68rVb
CG4VI5qK/wkML0jPQfNg/Q1d1Ak1MONhrrzLwqxeT2MXhBbxLPxWIMow5wGtQOVk
+qz8UjgXpWhZQG8wQzkO/GQCYALW+Y09aC4rtcQ8E2Z7mQPtkgX9fmtrFGWp6VWT
yoGXOrSM4isU8LsIXMckhBt5TjWoOxSxcy5dl0cyDcLhGF9PZZZVHfebujz+1j5l
43Owjf5otCBzRlFB4pMQ/sjjA9YYZh8XNSRA/rQJ1WE6UzA3TCHu7bHuSfqh14kh
tuIvluO3A/JcwJd1W3eNGO8/LPy4ZOnEfKRKFOjwrLygmZgdvuCSvVZh8e8VGPMU
lHD4c2BxNGJ/6I1n2y5FfIOPQPzyMUaxNeK0e6v6j1zLbs2j6T4lKzsOG5TxCAvQ
bjQTntu9rMnjHatfCWD7c0irKsV9pym3yCBx1wTyx03cMifzz8coREw19j6+kaml
IOqSVTDVgXC/XEIAvwPdEkDHMtjnBvwFmecXassp9biH8rYIhwzWfCo5f0rqBOhn
m8mTbaWMvnBPsglYR14BbejWoXU6um+94KzW6SjDcqA+Qy2Ismxfav+Tiwah6zCl
zzygc9WmkO2sEAKXYEHg
=e3Cv
-----END PGP SIGNATURE-----