From 584ce2f349e2f8f350826c88a21485132bafb8a4 Mon Sep 17 00:00:00 2001 From: Jason Molenda Date: Fri, 22 Mar 2013 00:38:45 +0000 Subject: [PATCH] Don't try to read the eh_frame section out of a dSYM. It won't have one and it isn't needed. llvm-svn: 177688 --- lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp b/lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp index 6f30932..069d23e 100644 --- a/lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp +++ b/lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp @@ -1477,7 +1477,11 @@ ObjectFileMachO::ParseSymtab (bool minimize) } else { - if (text_section_sp.get() && eh_frame_section_sp.get()) + // If m_type is eTypeDebugInfo, then this is a dSYM - it will have the load command claiming an eh_frame + // but it doesn't actually have the eh_frame content. And if we have a dSYM, we don't need to do any + // of this fill-in-the-missing-symbols works anyway - the debug info should give us all the functions in + // the module. + if (text_section_sp.get() && eh_frame_section_sp.get() && m_type != eTypeDebugInfo) { DWARFCallFrameInfo eh_frame(*this, eh_frame_section_sp, eRegisterKindGCC, true); DWARFCallFrameInfo::FunctionAddressAndSizeVector functions; -- 2.7.4