From: Blue Swirl <blauwirbel@gmail.com>
To: John Vele <jveleg@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Print input opcodes before translation
Date: Mon, 10 May 2010 23:10:42 +0300 [thread overview]
Message-ID: <v2yf43fc5581005101310r5bac0f5el72f2a8dfff2ad3de@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimToJmEiiOWFeOyRyzgCm854lqWbImzVUUjeTXv@mail.gmail.com>
On 5/10/10, John Vele <jveleg@gmail.com> wrote:
> Greetings,
>
> I'm using qemu user mode for i386 and I would like to print the opcodes of
> an
> input executable one bye one before any translation.
> Is the file target-i386/translate.c the one that I shall edit? The function
> disas_insn()
> in the same file is the appropriate one?
No need to edit anything, please RTFM for '-d in_asm' and
'-singlestep' parameters.
prev parent reply other threads:[~2010-05-10 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 20:05 [Qemu-devel] Print input opcodes before translation John Vele
2010-05-10 20:10 ` Blue Swirl [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=v2yf43fc5581005101310r5bac0f5el72f2a8dfff2ad3de@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=jveleg@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).