Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nikolay Martyanov <nmartyanov@ptsecurity.com>
To: <gdb@sourceware.org>
Subject: Re: Custom core file
Date: Wed, 28 Sep 2016 15:02:00 -0000	[thread overview]
Message-ID: <c545d565-9d5c-82a5-b1ec-2620736f043b@ptsecurity.com> (raw)
In-Reply-To: <fb396495-657e-1429-d773-f302171ae3b7@ptsecurity.com>

<http://www.securitylab.ru/>Thanks for response!

 > Then in the same python script execute dump/restore commands to load 
these into memory

I have tried to use "dump/restore" approach, but there is an issue.
When you use a restore command, you should already be in a context of 
debugging process.

I tried it like this:
1. Run GDB
2. Load symbols with  `file core.so`
3. Try to shove memory with `restore raw_mem.dump`
After that I have message: `You can't do that without a process to debug.`

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.

Am I wrong in my guesses?

Thanks,
Nikolay


  parent reply	other threads:[~2016-09-28 15:02 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
2016-09-28 15:02 ` Nikolay Martyanov [this message]
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=c545d565-9d5c-82a5-b1ec-2620736f043b@ptsecurity.com \
    --to=nmartyanov@ptsecurity.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