From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] backtrace() not working on ARMv7a
Date: Thu, 31 Jul 2014 08:39:43 +0200 [thread overview]
Message-ID: <20140731083943.49d4b0db@free-electrons.com> (raw)
In-Reply-To: <1406788255956-76350.post@n4.nabble.com>
Dear prafullakota,
On Wed, 30 Jul 2014 23:30:55 -0700 (PDT), prafullakota wrote:
> I am trying to generate a call stack trace using backtrace() API which is
> part of libbacktrace. The idea is to catch a SIGSEGV signal and call
> backtrace() to print all the address values and compare the obtained
> addresses from objdump -D of executable. Following is the output seen on
> ARMv7a platform with buildroot cross-toolchain (gcc- 4.8.2, binutis-2.18.1).
Thanks for the report. Could you provide your Buildroot .config so we
can see in more details what is your toolchain configuration
(especially which C library is used, and which version of it).
> For above issue uclibc forum has given fix in below link
> http://lists.uclibc.org/pipermail/uclibc/2013-September/047932.html
Right, but from a quick look, this patch was never applied.
> Similar issue in uclibc was solved by creating a patch to uclibc files, can
> some one let me know if there is any existing patch is available for glibc
> similar to this?, if not can anyone help me in providing the similar patch
> for glibc.
Are you sure you're using glibc ? Could you provide your
Buildroot .config file ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-31 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 6:30 [Buildroot] backtrace() not working on ARMv7a prafullakota
2014-07-31 6:39 ` Thomas Petazzoni [this message]
2014-07-31 7:47 ` prafulla_kota
2014-07-31 11:58 ` Thomas Petazzoni
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=20140731083943.49d4b0db@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.