Embedded Linux development
 help / color / mirror / Atom feed
From: Gilad Ben-Yossef <gilad@codefidence.com>
To: Marco Stornelli <marco.stornelli@coritel.it>
Cc: Linux-Embedded <linux-embedded@vger.kernel.org>
Subject: Re: Dump Management
Date: Tue, 01 Jul 2008 17:05:34 +0300	[thread overview]
Message-ID: <486A39AE.4040308@codefidence.com> (raw)
In-Reply-To: <4869DEF0.5060109@coritel.it>

hI,


Marco Stornelli wrote:

> what's the standard way to manage the core dump and therefore the 
> post-mortem debug? 
For most embedded systems I know, core dumps are useful on the developer 
desk and in the testing lab. For analyzing field post-mortem (where it 
is feasible), use a custom fault signal hander in your app to catch the 
relevant information and save it.

If you're interested in a tutorial in doing this, I'm giving one at this 
year OLS. Or you can just check out the slides and example code here:

http://tuxology.net/lectures/crash-and-burn-writing-linux-application-fault-handlers/ 

> For my experience it could be useful to have a mechanism to have 
> little dump image (only some information) to store it in flash and 
> maybe to have an hook (or something like this) for each application to 
> customize the dump information. What do you think about it?
>
That's exactly what a custom fault signal handler does :-)

Cheers,
Gilad

-- 
Gilad Ben-Yossef 
Chief Coffee Drinker

Codefidence Ltd.
The code is free, your time isn't.(TM)

Web:    http://codefidence.com
Email:  gilad@codefidence.com
Office: +972-8-9316883 ext. 201
Fax:    +972-8-9316885
Mobile: +972-52-8260388

	Q: How many NSA agents does it take to replace a lightbulb?
	A: dSva7DrYiY24yeTItKyyogFXD5gRuoRqPNQ9v6WCLLywZPINlu!


  reply	other threads:[~2008-07-01 14:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  7:38 Dump Management Marco Stornelli
2008-07-01 14:05 ` Gilad Ben-Yossef [this message]
2008-07-01 14:49   ` Marco Stornelli

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=486A39AE.4040308@codefidence.com \
    --to=gilad@codefidence.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=marco.stornelli@coritel.it \
    /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