[llvm-bugs] [Bug 23991] Memory managers should deregister EH frames in their destructor.

via llvm-bugs llvm-bugs at lists.llvm.org
Fri Dec 20 01:36:20 PST 2019


Lang Hames <lhames at gmail.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Lang Hames <lhames at gmail.com> ---
Hi Tom, Stefan,

A very belated update on this. I believe it *should* have been fixed for ORC by
r302589 / c936ac7f37dc.

EH-frame deregistration in MCJIT is still manual for backwards compatibility. 

> Will EH frame handling in JITLink be analogue to RuntimeDyld?

No: JITLink handles all of this differently. JITLink's memory managers are
responsible for memory management (and permission setting) only. EH-frame
registration/de-registration is handled by a plugin, and plugins are always
destroyed before the memory manager so these kinds of bugs (either leaking
registered frames, or deregistering them after freeing the underlying memory)
should not be possible.

-- Lang.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20191220/946bcabb/attachment.html>

More information about the llvm-bugs mailing list