From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Nikolay Martyanov <nmartyanov@ptsecurity.com>
Cc: gdb@sourceware.org
Subject: Re: Custom core file
Date: Wed, 28 Sep 2016 15:33:00 -0000 [thread overview]
Message-ID: <20160928153253.GA26040@host1.jankratochvil.net> (raw)
In-Reply-To: <d1f77270-0385-dbc2-078f-d9df17ce6f2d@ptsecurity.com>
On Wed, 28 Sep 2016 17:18:35 +0200, Nikolay Martyanov wrote:
> Idea is very similar to `kdump`, you are right. But instead of Linux kernel
> I have a hypervisor running on a bare-metal. So, in some point of view, I
> try to implement my own kdump. And it will dump not Linux kernel mem, but
> mem of hypervisor.
Ah, sorry I forgot you wrote that "bare-metal" there.
OK, so core files are not standardized the way executables+shlibs are by the
standards of ELF-generic and ELF-x86_64 or ELF-x86 addons. You can either
invent your own format (based on ELF or not) or - what I suggest - is to just
mimic the Linux kernel process format.
In fact /proc/kcore and kdump also create a core file looking as a userland
process to make it easier for consumers to read it, despite the content is
unrelated to userland processes.
I am not aware of official Linux core file documentation, it is best to read
sources in its producers (Linux kernel, gdb gcore) + consumers (many)
Jan
next prev parent reply other threads:[~2016-09-28 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 13:31 Nikolay Martyanov
2016-09-28 14:28 ` Duane Ellis
2016-09-28 14:58 ` Jan Kratochvil
2016-09-28 15:18 ` Nikolay Martyanov
2016-09-28 15:33 ` Jan Kratochvil [this message]
2016-09-28 16:27 ` Nikolay Martyanov
2016-09-28 15:02 ` Nikolay Martyanov
2016-09-28 15:31 duane
2016-09-28 16:37 ` Nikolay Martyanov
2016-09-28 19:22 ` Nikolay Martyanov
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=20160928153253.GA26040@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=nmartyanov@ptsecurity.com \
/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