From: Clemens Kolbitsch <ck@iseclab.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] x86 opcode length
Date: Mon, 19 May 2008 12:05:27 +0200 [thread overview]
Message-ID: <200805191205.27881.ck@iseclab.org> (raw)
Hi!
I'm working on a project that needs to copy out the currently executing x86
opcode (I have disabled block chaining for this) under certain conditions...
is there a way to figure out, exactly how long the original opcode of the TB
was (i.e. including prefixes, parameters, etc.)?
I know that the information is encoded implicitly in the disas_insn
function... but maybe there is a function somewhere that does exactly this or
someone of you has a handy table/documentation for this.
Thx!
Clemens
reply other threads:[~2008-05-19 10:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200805191205.27881.ck@iseclab.org \
--to=ck@iseclab.org \
--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).