search for: lc_dysymtab

....o file. I'm parsing the MACH-O executable, which has a LC_SYMTAB entry, and one of the entries is the file path of the .o file. So I can find the file that way. Then I parse the MACH-O .o file, which also has the LC_SYMTAB, as well as an LC_SEGMENT_64 and LC_DATA_IN_CODE, and then finally a LC_DYSYMTAB. But I don't see where the address-to-line information is, or any DWARF information. Where is LLDB getting this address-to-line info? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180823/a5cf277a/attac...

...CED attributes NO_TOC STRIP_STATIC_SYMS LIVE_SUPPORT reserved1 0 reserved2 0 Load command 1 cmd ?(0x00000029) Unknown load command cmdsize 16 00000b50 00000008 Load command 2 cmd LC_SYMTAB cmdsize 24 symoff 2904 nsyms 17 stroff 3176 strsize 312 Load command 3 cmd LC_DYSYMTAB cmdsize 80 ilocalsym 0 nlocalsym 15 iextdefsym 15 nextdefsym 2 iundefsym 17 nundefsym 0 tocoff 0 ntoc 0 modtaboff 0 nmodtab 0 extrefsymoff 0 nextrefsyms 0 indirectsymoff 0 nindirectsyms 0 extreloff 0...

Hi Kent, My guess is you are getting some new bit of info in your object files and your ranlib(1) is older and doesn't know about it. If you can send me the .o file or the output of otool(1) with the -hlv options on your object file I can take a look. Kev P.S. you can find out the version of ranlib(1) you have by running strings(1) on it and grep(1)'ing for the string

Ran into this today -- rebuilt the SVN Trunk for this morning of LLVM+CLANG. Now every time my builds try and make a library from .o files, ranlib complains about 'malformed object' files. This is with OS X 10.7.4, and the binary tools from XCode 4.4.1 ld -v @(#)PROGRAM:ld PROJECT:ld64-127.2 llvm version 3.0svn, from Apple Clang 3.0 (build 211.12) ranlib doesn't tell you what