[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <8EEA4EA8-D626-4498-B2D6-866D3F4655E2@wardco.com>
Date: Tue, 19 Jan 2016 10:23:32 -0800
From: Ward Willats <musl@...dco.com>
To: musl@...ts.openwall.com
Subject: Re: MUSCL + MIPS + threads + debugging/stack traces
> On Jan 19, 2016, at 4:45 AM, Felix Fietkau <nbd@...nwrt.org> wrote:
> On 2016-01-19 05:19, Rich Felker wrote:
>> On Mon, Jan 18, 2016 at 05:34:27PM -0800, Ward Willats wrote:
>>> When we try to get a backtrace with the toolchain gdb/gdbserver (or
>>> the latest one we cross compiled ourselves from source) we get these
>>> kind of pathetic, truncated stack traces.
>>
>> It looks like your libc build lacks debug info and thus gdb is
>> attempting to use heuristics to make sense of the call stack.
> Seems that I forgot to put in --enable-debug in the Makefile. This is
> fixed in r48363 now.
>
Ha! Turning debug on makes things great. Core dumps too. (At least as far as our quick checks this morning go.)
And boy, do we feel like idiots for not figuring this out straight away! Seems so obvious in retrospect.
Thank you all.
-- Ward
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
