From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Bob Breuer <breuerr@mc.net>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] tracetool parse problem for parenthesis in format string
Date: Thu, 17 May 2012 09:41:09 +0100 [thread overview]
Message-ID: <20120517084109.GA6516@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <4FA200E7.5030309@mc.net>
On Wed, May 02, 2012 at 10:52:07PM -0500, Bob Breuer wrote:
> The new tracetool has a problem with parsing parenthesis within the
> format string. For example, add this line to trace-events:
> test_paren(int n) "(%d)"
> and you will get a failure when generating trace.h.
Thanks for reporting this bug. I just got back from vacation but will
try to get a fix out if it hasn't been addressed already.
Stefan
prev parent reply other threads:[~2012-05-17 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 3:52 [Qemu-devel] tracetool parse problem for parenthesis in format string Bob Breuer
2012-05-17 8:41 ` Stefan Hajnoczi [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=20120517084109.GA6516@stefanha-thinkpad.localdomain \
--to=stefanha@linux.vnet.ibm.com \
--cc=breuerr@mc.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).