From: Nikolay Martyanov <nmartyanov@ptsecurity.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: <gdb@sourceware.org>
Subject: Re: Custom core file
Date: Wed, 28 Sep 2016 16:27:00 -0000 [thread overview]
Message-ID: <c2501bb2-29a1-702b-50a1-fbb9522b63bc@ptsecurity.com> (raw)
In-Reply-To: <20160928153253.GA26040@host1.jankratochvil.net>
On 09/28/2016 06:32 PM, Jan Kratochvil wrote:
> 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.
>
> 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.
>
>
Not sure I can mimic Linux format exactly. At least I have another set
of registers in use (VMX of Intel x86 arch are involved). May be it's
critical, may be not...
Any way, Linux code was the first thing I looked at. So my way is "mimic
as close as possible, adapt as few as possible".
Thanks for confirmation that it is one of possible ways to solve my
problem =)
And in case I can't mimic it for 100%, I have to make several
adaptations in GDB. The details were listed in my first message.
Still hoping someone can comment on them
Thanks,
Nikolay
next prev parent reply other threads:[~2016-09-28 16:27 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
2016-09-28 16:27 ` Nikolay Martyanov [this message]
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=c2501bb2-29a1-702b-50a1-fbb9522b63bc@ptsecurity.com \
--to=nmartyanov@ptsecurity.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.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