https://llvm.org/bugs/show_bug.cgi?id=26191
Bart Jacobs <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #7 from Bart Jacobs <[email protected]> --- I think I figured out why people say the x86_64 ABI requires .eh_frame. The main reason is: being able to get a correct backtrace, even in the absence of debug symbols, is considered important for diagnosis and monitoring. Putting the info in the .debug_frame section means it is only there in debug builds, and it gets stripped when stripping debug info. That is considered undesirable. I can appreciate that. Still, I wish the use case of generating a backtrace were separated from the use case of exception handling. In particular, I wish the Objective-C runtime (through libunwind) did not interpret the presence of .eh_frame in my OCaml binary as an invitation to walk into my OCaml stack frames (and crash on the incorrect unwind info). I wish it were possible to mark frames as "exception-safe" or not and to have the Objective-C runtime not walk into frames not marked as exception-safe. But that's a separate request, I guess. So I'm marking this as resolved. -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ llvm-bugs mailing list [email protected] http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
