You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implementing the _Unwind level of the APIs discussed in the above link, will, I think, allow us to directly reuse the actual implementation of the libcxxabi from LLVM to deal accurately with C++ exceptions. AFAICT, all the magic stack introspection steps actually happen inside libunwind, and is therefore an appropriate abstraction layer for override implementation inside Crucible.
I haven't completely convinced myself that the operations so described are actually reasonable to bolt onto crucible, but it doesn't seem impossible.
The text was updated successfully, but these errors were encountered:
CF http://refspecs.linuxfoundation.org/abi-eh-1.22.html
Implementing the
_Unwind
level of the APIs discussed in the above link, will, I think, allow us to directly reuse the actual implementation of thelibcxxabi
from LLVM to deal accurately with C++ exceptions. AFAICT, all the magic stack introspection steps actually happen insidelibunwind
, and is therefore an appropriate abstraction layer for override implementation inside Crucible.I haven't completely convinced myself that the operations so described are actually reasonable to bolt onto crucible, but it doesn't seem impossible.
The text was updated successfully, but these errors were encountered: