On Tue, Apr 3, 2018 at 7:24 AM, Greg Clayton <clayb...@gmail.com> wrote: > > >> On Apr 2, 2018, at 10:27 AM, Davide Italiano <dccitali...@gmail.com> wrote: >> >> Now with the correct e-mail. >> How is this different from llvm-objdump or llvm-readobj? > > It was originally created for parsing .a files and getting the mod date as a > hex number from the BSD object info. I needed a tool that could verify a > debug map that used .a files. There are build scenarios where people are > seeing LLDB not load .o files from .a files and they don't know why. This > installs an LLDB command that can be used to verify all of the .o files in a > debug map and reports if they are all ok, or if any are out date, missing, > wrong in the .a file, missing from the .a file, etc. You can't use > llvm-objdump or llvm-readobj for this task. >
I see, I would've built that on top of lib/Archive, but given you wrote the code, I won't complain :) > It can also extract individual .o files from a .a file. > FWIW, A BSD archive can be opened with any archiver you want, including, e.g. Winrar. > It can also find a symbol in the __.SYMDEF to tell you which .a file contains > a symbol by name. > llvm-readobj/llvm-objdump don't implement this just because nobody wanted to, but I don't see why it wouldn't be possible (if we really wanted it). Thanks, -- Davide _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
