From: Ward Willats <musl@wardco.com>
To: musl@lists.openwall.com
Subject: Re: MUSCL + MIPS + threads + debugging/stack traces
Date: Tue, 19 Jan 2016 10:23:32 -0800 [thread overview]
Message-ID: <8EEA4EA8-D626-4498-B2D6-866D3F4655E2@wardco.com> (raw)
In-Reply-To: <569E2FEB.3090305@openwrt.org>
> On Jan 19, 2016, at 4:45 AM, Felix Fietkau <nbd@openwrt.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
prev parent reply other threads:[~2016-01-19 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 1:34 Ward Willats
2016-01-19 4:19 ` Rich Felker
2016-01-19 12:45 ` Felix Fietkau
2016-01-19 18:23 ` Ward Willats [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8EEA4EA8-D626-4498-B2D6-866D3F4655E2@wardco.com \
--to=musl@wardco.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).