From: Marco Stornelli <marco.stornelli@coritel.it>
To: Gilad Ben-Yossef <gilad@codefidence.com>
Cc: Linux-Embedded <linux-embedded@vger.kernel.org>
Subject: Re: Dump Management
Date: Tue, 01 Jul 2008 16:49:51 +0200 [thread overview]
Message-ID: <486A440F.5000709@coritel.it> (raw)
In-Reply-To: <486A39AE.4040308@codefidence.com>
Gilad Ben-Yossef ha scritto:
> 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
>
Very interesting....Thanks.
--
Marco Stornelli
Embedded Software Engineer
CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
http://www.coritel.it
marco.stornelli@coritel.it
+39 06 72582838
prev parent reply other threads:[~2008-07-01 14:49 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
2008-07-01 14:49 ` Marco Stornelli [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=486A440F.5000709@coritel.it \
--to=marco.stornelli@coritel.it \
--cc=gilad@codefidence.com \
--cc=linux-embedded@vger.kernel.org \
/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