From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: John Smith <horserivers@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: examine memory coomand
Date: Mon, 20 Aug 2012 08:34:00 -0000 [thread overview]
Message-ID: <20120820083421.GA20446@host2.jankratochvil.net> (raw)
In-Reply-To: <CAJR88phg3Z2tC4LJvTzw1CHdkYjD9qxJdQ+fBeujT41HbfWg6w@mail.gmail.com>
On Mon, 20 Aug 2012 10:27:12 +0200, John Smith wrote:
> when gdb try to get memory data from "examine " command , is it
> get data from pythical memory with a "mov" operation or from
> memory map file?
Assuming GNU/Linux OS here.
It is read by PTRACE_PEEKDATA or from /proc/PID/mem. It is virtual address
space of the process (not physical memory), as provided by kernel.
Jan
prev parent reply other threads:[~2012-08-20 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 8:27 John Smith
2012-08-20 8:34 ` Jan Kratochvil [this message]
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=20120820083421.GA20446@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=horserivers@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).