[Bug binutils/19435] New: objdump receives SIGABRT when disassembling Mach O binary on OS X

[iankronquist at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19435

            Bug ID: 19435
           Summary: objdump receives SIGABRT when disassembling Mach O
                    binary on OS X
           Product: binutils
           Version: 2.25
            Status: NEW
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: iankronquist at gmail dot com
  Target Milestone: ---

Created attachment 8887
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8887&action=edit
C Source code which can cause objdump to fail

On OS X 10.11, given certain Mach-O x86_64 binaries compiled with the '-g' flag
objdump vversion 2.25 receives SIGABRT when attempting to free a pointer which
was never allocated. It should at least fail gracefully, but preferably should
not fail at all.
Steps to reproduce:
Given the attached C source file, compile it with the '-g' flag with GCC 5.3.0
or clang Apple LLVM version 7.0.0 (clang-700.1.76).

$ gcc -g out.c
OR
$ clang -g out.c

Now run disassemble the resulting binary with the '-S' flag to mix in source
code with the binary:
$ objdump -S a.out

./a.out:     file format mach-o-x86-64


Disassembly of section .text:
... many correct assembly instructions ...
gobjdump(13297,0x7fff791b1000) malloc: *** error for object 0x101203e00:
pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Abort trap: 6

For your convenience, a binary which causes these problems is attached.

I would be willing to do further investigation into this, and, if I am not too
busy and this looks relatively approachable, work on providing a patch.

-- 
You are receiving this mail because:
You are on the CC list for the bug.