From: Nikolay Martyanov <nmartyanov@ptsecurity.com>
To: <duane@duaneellis.com>, <gdb@sourceware.org>
Subject: Re: Custom core file
Date: Wed, 28 Sep 2016 16:37:00 -0000 [thread overview]
Message-ID: <55af2d92-9c32-2bd0-22e4-c869f3afe14d@ptsecurity.com> (raw)
In-Reply-To: <20160928083121.5c1bb9f86d671edec44bb378f25c04cc.5416b9a60c.wbe@email03.godaddy.com>
On 09/28/2016 06:31 PM, duane@duaneellis.com wrote:
>>> So, I guess, dump/restore approach works only in two cases:
>>> a) debugging live process you have attached to (it's not my case, as I
>>> perform postmortem debug)
>>> b) already has loaded core file, which provides a context via saved CPU
>>> state - and it is the way I chose to follow.
> For step (B) - first load a dummy (tiny) standard core file - that gives
> you a debug context, think of it as a shim.
Is it a common case for GDB? Can this "fake" context bring me some
erroneous debug info?
I had such an idea, but due to doubt I mentioned above, decided not even
to try. Now I will =)
Thanks,
Nikolay
<http://www.securitylab.ru/>
next prev parent reply other threads:[~2016-09-28 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 15:31 duane
2016-09-28 16:37 ` Nikolay Martyanov [this message]
2016-09-28 19:22 ` Nikolay Martyanov
-- strict thread matches above, loose matches on Subject: below --
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
2016-09-28 15:02 ` 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=55af2d92-9c32-2bd0-22e4-c869f3afe14d@ptsecurity.com \
--to=nmartyanov@ptsecurity.com \
--cc=duane@duaneellis.com \
--cc=gdb@sourceware.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