search for: __registerframe

Yaron, Did you find a way around the problem? It looks like the problem comes before processFDE because by the time it gets to processFDE the eh_frame data is already corrupted. Does ELF and MachO share the same eh_frame format? I am developing this code in parallel on an Ubuntu Linux system but I haven't tried to run it on there for a couple of weeks. I'll bring it up to date and

...l .eh_frames are combined. The dynamic linker must perform the same function, else __register_frame(.eh_frame) might continue processing after .eh_frame, depending if there were four zero bytes following it - or not - by chance. However this again isn't likely to be your source of problem, as __registerframe on OS-X processes one FDE at the time and the calling function processFDE() in RTDyldMemoryManager.cpp does know the size of eh_frame so it will not overrun the frame. The solution would be to allocate a larger buffer, copy .eh_frame into it with four zero bytes appended. This buffer needs to liv...

Hi, I had similar problems with EH in ELF in RTDyldMemoryManager::registerEHFrames() calling __register_frame(). I'm not sure these problems are related to this problem since your crash happens in RuntimeDyldMachO::registerEHFrames() in its own processFDE (there are two functions named processFDE(), one in RuntimeDyldMachO.cpp and one in RTDyldMemoryManager.cpp) *before*