From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: t cheney <cdmalord@gmail.com>
Cc: gdb <gdb@sourceware.org>,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org,
crash-catcher@lists.fedorahosted.org
Subject: Re: [PATCH 1/1] x86: Add process memory layout to coredump file
Date: Mon, 12 Dec 2011 22:03:28 +0100 [thread overview]
Message-ID: <20111212210328.GA29248@host2.jankratochvil.net> (raw)
In-Reply-To: <CAE04G=D_OzrDRUOj-iVPJY5sNTLMfUKAeikks8TWMYOWvh6HeA@mail.gmail.com>
On Sun, 11 Dec 2011 15:10:00 +0100, t cheney wrote:
> This patch just add memory layout(same as /proc/pid/maps) to
> coredump file. The layout is appended to corenote segment with
> flag NT_MAPS=7.
FYI this has been solved by ABRT - Automated Bug-Reporting Tool
https://fedorahosted.org/abrt/
(it is distro-neutral despite its homepage)
Core file is there a subdirectory where the core file is just one of the many
associated files:
/var/spool/abrt/ccpp-*:
abrt_version analyzer architecture cmdline component coredump count
dso_list environ executable hostname kernel maps os_release package
pid pwd reason time uid username uuid var_log_messages
More info files are being continually added, such as /proc/PID/fd{,info}/
mapping at the crash dump time etc. You would need to add many more core file
notes to make the core files useful for later analysis.
Regards,
Jan
next prev parent reply other threads:[~2011-12-12 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 14:37 [PATCH 1/1] x86: Add process memory layout to coredump file t cheney
2011-12-10 20:02 ` Andi Kleen
2011-12-11 12:44 ` t cheney
2011-12-11 13:19 ` t cheney
[not found] ` <CAE04G=D_OzrDRUOj-iVPJY5sNTLMfUKAeikks8TWMYOWvh6HeA@mail.gmail.com>
2011-12-12 21:03 ` Jan Kratochvil [this message]
2011-12-18 10:10 ` t cheney
2011-12-14 21:16 ` Al Viro
2011-12-18 12:37 ` t cheney
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=20111212210328.GA29248@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=cdmalord@gmail.com \
--cc=crash-catcher@lists.fedorahosted.org \
--cc=gdb@sourceware.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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