From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: Davide Ferraretto <femudevelopment@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Read location of memory poits esp register
Date: Tue, 8 May 2012 00:10:04 +0700 [thread overview]
Message-ID: <CAGdaadbVKCxifsL-5gZg+oeermQuhXxj7ogV48HNX_f11_hqsw@mail.gmail.com> (raw)
In-Reply-To: <4FA7FD02.6050104@gmail.com>
On Mon, May 7, 2012 at 11:49 PM, Davide Ferraretto
<femudevelopment@gmail.com> wrote:
> how can I read location of memory poits by esp register (i386 cpu)??
>
>
CMIIW, using gdb stub hooked to Qemu, it should be:
p $esp
<get the number>
x <from the number above>
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2012-05-07 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 16:49 [Qemu-devel] Read location of memory poits esp register Davide Ferraretto
2012-05-07 17:10 ` Mulyadi Santosa [this message]
2012-05-07 17:18 ` Davide Ferraretto
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=CAGdaadbVKCxifsL-5gZg+oeermQuhXxj7ogV48HNX_f11_hqsw@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=femudevelopment@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).