From: "Peter Kümmel" <syntheticpp@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] backtrace() depth
Date: Tue, 10 Sep 2013 21:18:38 +0200 [thread overview]
Message-ID: <522F708E.2070004@gmx.net> (raw)
I've a question about the depth of a backtrace.
I've configured uClibc/Buildroot to build libubacktrace-0.9.33.2.so
via the standard Buildroot menuconfigs:
Buildroot 2013.02, GCC 4.7.2 by Buildroot, uClibc-0.9.33
When I call backtrace() on a segfault, I only see the function
where the segfault is produced, and not much more (only /lib/libc.so.0,
and two more addresses). The function name could be demanded correctly,
so I assume the compiler flags are ok (-rdynamic).
The segfault is not in the main thread
(overall 4 threads, /lib/libpthread-0.9.33.2.so)
And the bt looks equal for debug and release builds.
A build with crosstool-ng and eglibc produces the same bad backtrace.
Is there a way to get a more complete backtrace?
Many thanks,
Peter
next reply other threads:[~2013-09-10 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 19:18 Peter Kümmel [this message]
2013-09-10 19:40 ` [Buildroot] backtrace() depth Samuel Martin
2013-09-10 19:53 ` Peter Kümmel
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=522F708E.2070004@gmx.net \
--to=syntheticpp@gmx.net \
--cc=buildroot@busybox.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.