bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/19435] objdump receives SIGABRT when disassembling Mach O


From: iankronquist at gmail dot com
Subject: [Bug binutils/19435] objdump receives SIGABRT when disassembling Mach O binary on OS X
Date: Fri, 08 Jan 2016 10:02:22 +0000

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

--- Comment #4 from Ian Kronquist <iankronquist at gmail dot com> ---
Nick,
The problem is mach-o specific. The problem persists under mainline
binutils built on OS X. I attached a problematic mach-o which you could try
to disassemble as described previously. The problem is in the function
bfd_mach_o_close_and_cleanup, probably in the only invocation of free in
that function. My guess is that some of the bfd metadata is messed up and
never properly allocated, but I'm not sure. I'll have to do some more
investigation. I'm willing to try to help fix the bug and submit a patch if
I can get some guidance.

Thanks,
Ian
On Jan 8, 2016 1:53 AM, "nickc at redhat dot com" <
address@hidden> wrote:

> https://sourceware.org/bugzilla/show_bug.cgi?id=19435
>
> Nick Clifton <nickc at redhat dot com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |nickc at redhat dot com
>
> --- Comment #3 from Nick Clifton <nickc at redhat dot com> ---
> Hi Ian,
>
>   Unfortunately I am unable to reproduce this problem using an x86_64 Linux
> hosted cross compiler.  Possibly the problem is Mach-O specific.
>
>   Please could you check to see if the problem is still present with the
> current mainline binutils development sources.
>
>   If the problem does still exist, please you try to narrow down where
> the  bug
> is occurring.  Ie where is the free() happening ?
>
> Cheers
>   Nick
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You reported the bug.

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]