From: cmc2001 <craig.mcfarlane@pri.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] Core Files on ARM
Date: Sun, 14 Mar 2010 21:43:17 -0700 (PDT) [thread overview]
Message-ID: <27900409.post@talk.nabble.com> (raw)
TWIMC,
Forgive the noob question, but we have a busybox'd target which we've
configured to produce partial core files when our app crashes. However, it
seems to only have spotty backtrace information - specifically, only a stack
trace for one thread.
Busybox 1.13.4
g++ 4.2.1
kernel 2.6.28.2
I know I'm not alone after trawling google, but I'm yet to find anything
approaching a definitive answer.
I've been banging my head on this problem for several days now and the more
I dig, the more possible problems I discover (the latest being the g++ ARM
toolchain and its limitations). Would this corefile problem be resolved if
I moved up to:
Busybox 1.15.3
gcc 4.4.3
kernel 2.6.29.4
Also, if Busybox's menus is dumbing down my control of corefiles a little
too much, is there an agreed way of subverting it that won't get me into
trouble down the track?
cya
Craig
--
View this message in context: http://old.nabble.com/Core-Files-on-ARM-tp27900409p27900409.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next reply other threads:[~2010-03-15 4:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 4:43 cmc2001 [this message]
2010-03-15 6:44 ` [Buildroot] Core Files on ARM cmc2001
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=27900409.post@talk.nabble.com \
--to=craig.mcfarlane@pri.com.au \
--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.