All of lore.kernel.org
 help / color / mirror / Atom feed
From: prafulla_kota <prafulla.kota@broadcom.com>
To: buildroot@busybox.net
Subject: [Buildroot] backtrace() not working on ARMv7a
Date: Thu, 31 Jul 2014 00:47:34 -0700 (PDT)	[thread overview]
Message-ID: <1406792854426-76360.post@n4.nabble.com> (raw)
In-Reply-To: <20140731083943.49d4b0db@free-electrons.com>

Hi Thomas, 

Thanks for quick reply and i have attached the .config file. 

We have applied below patch in ulibc and it worked fine for below
requirement and we do have requirement on GLIBC as well and requesting the
same here. 

Thanks, 
Prafulla kota

buildroot_dot_config.buildroot_dot_config
<http://buildroot-busybox.2317881.n4.nabble.com/file/n76360/buildroot_dot_config.buildroot_dot_config>  



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/backtrace-not-working-on-ARMv7a-tp76350p76360.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

  reply	other threads:[~2014-07-31  7:47 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
2014-07-31  7:47   ` prafulla_kota [this message]
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=1406792854426-76360.post@n4.nabble.com \
    --to=prafulla.kota@broadcom.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.