From: Stuart Anderson <anderson@netsweng.com>
To: Mulyadi Santosa <a_mulyadi@softhome.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] strace-like output for user-linux
Date: Sun, 3 Jun 2007 13:34:36 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706031334160.21792@trantor.stuart.netsweng.com> (raw)
In-Reply-To: <4662FD59.40806@softhome.net>
On Mon, 4 Jun 2007, Mulyadi Santosa wrote:
> Hi Stuart
>
> I hope my little advice is correct... but overall, I think you add a nice
> usefuk feature here.
>
> + }--> don't you think we should break() here since we already found
> correct syscall num? otherwise we will continue the loop
Yes indeed. Thanks for catching that.
Stuart
Stuart R. Anderson anderson@netsweng.com
Network & Software Engineering http://www.netsweng.com/
1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F
BD03 0A62 E534 37A7 9149
prev parent reply other threads:[~2007-06-03 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 16:35 [Qemu-devel] [RFC] strace-like output for user-linux Stuart Anderson
2007-06-03 17:41 ` Mulyadi Santosa
2007-06-03 17:34 ` Stuart Anderson [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=Pine.LNX.4.64.0706031334160.21792@trantor.stuart.netsweng.com \
--to=anderson@netsweng.com \
--cc=a_mulyadi@softhome.net \
--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).