tree 319d560e9e31d947158f42791ff559dcdf3035cb
parent c9ae673bcf1d1d2acb1b3a58a91d1d851b3a93d7
author Martin Storsjö <martin@martin.st> 1574862953 +0200
committer Copybara-Service <copybara-worker@google.com> 1604019963 -0700

[libunwind] [SEH] Don't interact with foreign exceptions

This unfortunately means that we don't execute C++ destructors when
unwinding past such frames for a different SEH unwind purpose (e.g.
as part of setjmp/longjmp), but that case isn't handled properly at
the moment (the original unwind intent is lost and we end up with an
unhandled exception). This patch makes sure the foreign unwind terminates
as intended.

After executing a handler, _Unwind_Resume doesn't have access to
the target frame parameter of the original foreign unwind. We also
currently blindly set ExceptionCode to STATUS_GCC_THROW - we could
set that correctly by storing the original code in _GCC_specific_handler,
but we don't have access to the original target frame value.

This also matches what libgcc's SEH unwinding code does in this case.

Differential Revision: https://reviews.llvm.org/D89231

GitOrigin-RevId: fc5e68fab965bdc8fdf6db9ae2603f9dd02dec5b