From: "Shashidhar Mysore" <shashimc@gmail.com>
To: qemu-devel@nongnu.org, alfius@freemail.gr
Subject: Re: [Qemu-devel] Re: Full instruction tracing
Date: Fri, 13 Apr 2007 18:34:47 -0700 [thread overview]
Message-ID: <12835c8f0704131834m72ecf1bcob3e5e4653d5b9512@mail.gmail.com> (raw)
In-Reply-To: <876480rt91.fsf@brigitte.dna.fi>
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
Both the methods discussed in the past thread (which Antti pointed in the
previous mail) worked well for me.
-Shashi.
On 4/13/07, Antti P Miettinen <ananaza@iki.fi> wrote:
>
> Alexandros Frantzis <alfius@freemail.gr> writes:
> > Can someone give me some pointers on how this might be implemented in
> > qemu (if it doesn't already exist)?
>
> There was recently a thread about this:
>
> http://thread.gmane.org/gmane.comp.emulators.qemu/16604
>
> --
> http://www.iki.fi/~ananaza/
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 953 bytes --]
prev parent reply other threads:[~2007-04-14 1:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 10:52 [Qemu-devel] Full instruction tracing Alexandros Frantzis
2007-04-13 19:04 ` [Qemu-devel] " Antti P Miettinen
2007-04-14 1:34 ` Shashidhar Mysore [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=12835c8f0704131834m72ecf1bcob3e5e4653d5b9512@mail.gmail.com \
--to=shashimc@gmail.com \
--cc=alfius@freemail.gr \
--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).