From: cmc2001 <craig.mcfarlane@pri.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] Core Files on ARM
Date: Sun, 14 Mar 2010 23:44:41 -0700 (PDT) [thread overview]
Message-ID: <27900834.post@talk.nabble.com> (raw)
In-Reply-To: <27900409.post@talk.nabble.com>
cmc2001 wrote:
>
> Forgive the noob question, but we have a busybox'd target which we've
> configured to produce partial core files when our app crashes.
OK, it was obviously a bigger noob question than I realised. I realise now
that buildroot sits at the top of the tree, not BusyBox.
Would I be right in saying that the BR2_PTHREAD_DEBUG flag is for debugging
the pthread library, not so much producing better thread info in application
core files?
I didn't run across an obvious setting for enabling complete core files in
Config.in. Where exactly would such a beast live? Is there a separate
Config.in for kernel-specific stuff?
cya
Craig
--
View this message in context: http://old.nabble.com/Core-Files-on-ARM-tp27900409p27900834.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
prev parent reply other threads:[~2010-03-15 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 4:43 [Buildroot] Core Files on ARM cmc2001
2010-03-15 6:44 ` cmc2001 [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=27900834.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox