This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libbacktrace and darwin

On Oct 5, 2012, at 11:37 AM, Richard Guenther wrote:

> On Fri, Oct 5, 2012 at 9:15 AM, Tristan Gingold <> wrote:
>> On Oct 4, 2012, at 11:23 PM, Ian Lance Taylor wrote:
>>> On Thu, Oct 4, 2012 at 1:32 PM, Jack Howarth <> wrote:
>>>>  Is libbacktrace currently functional in gcc trunk and is it expected
>>>> to function on darwin? While I could understand it not working on installed
>>>> binaries of FSF gcc that were stripped, I would think it should work for
>>>> make check in the build tree since all of the debug code should be present
>>>> in the object files. Or doesn't libbacktrace know to look there for the
>>>> dwarf code? Thanks in advance for any clarifications.
>>> libbacktrace is functional in GCC trunk.  However, it does not yet
>>> support the Mach-O object file format.  I hope to work on that at some
>>> point, but it would be great if somebody else tackled it.  It's
>>> probably straightforward to implement based on code in
>>> libiberty/simple-object-mach-o.c.
>> I doubt it will, as dwarf info aren't in the executable.  I think it will be
>> simpler to support .dsym (separate debug file) at first.
> So I take it that libbacktrace doesn't work with the separate DWARF
> debuginfo as shipped by all Linux distributions either?

I don't know, but the Mach-O mechanism to get the separate debug file is different from ELF.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]