From: Marco Stornelli <marco.stornelli@coritel.it>
To: Linux-Embedded <linux-embedded@vger.kernel.org>
Subject: Dump Management
Date: Tue, 01 Jul 2008 09:38:24 +0200 [thread overview]
Message-ID: <4869DEF0.5060109@coritel.it> (raw)
Hi,
what's the standard way to manage the core dump and therefore the
post-mortem debug? 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?
Regards,
--
Marco Stornelli
Embedded Software Engineer
CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
http://www.coritel.it
marco.stornelli@coritel.it
+39 06 72582838
next reply other threads:[~2008-07-01 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 7:38 Marco Stornelli [this message]
2008-07-01 14:05 ` Dump Management Gilad Ben-Yossef
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=4869DEF0.5060109@coritel.it \
--to=marco.stornelli@coritel.it \
--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 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.