[llvm-bugs] [Bug 31752] New: llvm-objdump won't disassemble the whole text section

[via llvm-bugs]

https://llvm.org/bugs/show_bug.cgi?id=31752

            Bug ID: 31752
           Summary: llvm-objdump won't disassemble the whole text section
           Product: new-bugs
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: hanauska at equinux.com
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

Recently I wanted to disassemble the text section of a mach-o binary. The text
section is almost 4 MB in size, but otool only disassembles the last 27 KB of
it. It starts disassembling at the first known symbol and as the binary was
heavily stripped and optimized, there were almost no symbols in the final
binary. I reported that bug to Apple and here is what they said:

> Engineering has determined that this issue behaves as intended 
> based on the following information: 
> 
> The implementation of otool(1) changed in Xcode 8 to be based
> on llvm-objdump(1) from the old otool-classic(1), which is
> still on the system.
>
> For the llvm community, the current behavior of starting
> disassembly from the first known symbol is the behavior the
> llvm community desires.

So basically Apple points with the finger on you and says it's your fault.
Well, I am part of that community and wanted to let you know that this is
absolutely undesired behavior. I don't understand that behavior and I don't
want it either. Using otool-classic the whole section is disassembled which
saved my day but I don't want to reply that Apple will keep that one around for
ever.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170125/59616f7b/attachment.html>