On Fri, Oct 5, 2012 at 2:37 AM, Richard Guenther
wrote:
>
> So I take it that libbacktrace doesn't work with the separate DWARF
> debuginfo as shipped by all Linux distributions either?
That does not work at present. I doubt it's difficult.
Ian
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
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 understa
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 str
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
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
