From: Eric Auger <eric.auger@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: "Lluís Vilanova" <vilanova@ac.upc.edu>
Subject: Re: [Qemu-devel] [PATCH v2] trace: tighten up trace-events regex to fix bad parse
Date: Tue, 30 Sep 2014 08:32:58 +0200 [thread overview]
Message-ID: <542A4E9A.5010600@linaro.org> (raw)
In-Reply-To: <1411468626-20450-1-git-send-email-stefanha@redhat.com>
Dear all,
this patch fixes the issues I reported (related to VFIO trace points).
Many thanks for that.
Best Regards
Eric
On 09/23/2014 12:37 PM, Stefan Hajnoczi wrote:
> Use \w for properties and trace event names since they are both drawn
> from [a-zA-Z0-9_] character sets.
>
> The .* for matching properties was too aggressive and caused the
> following failure with foo(int rc) "(this is a test)":
>
> Traceback (most recent call last):
> File "scripts/tracetool.py", line 139, in <module>
> main(sys.argv)
> File "scripts/tracetool.py", line 134, in main
> binary=binary, probe_prefix=probe_prefix)
> File "scripts/tracetool/__init__.py", line 334, in generate
> events = _read_events(fevents)
> File "scripts/tracetool/__init__.py", line 262, in _read_events
> res.append(Event.build(line))
> File "scripts/tracetool/__init__.py", line 225, in build
> return Event(name, props, fmt, args, arg_fmts)
> File "scripts/tracetool/__init__.py", line 185, in __init__
> % ", ".join(unknown_props))
> ValueError: Unknown properties: foo(int, rc)
>
> Cc: Lluís Vilanova <vilanova@ac.upc.edu>
> Reported-by: Eric Auger <eric.auger@linaro.org>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> v2:
> * Fix regex to allow multiple properties [Lluís]
>
> scripts/tracetool/__init__.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/tracetool/__init__.py b/scripts/tracetool/__init__.py
> index 36c789d..6ee6af7 100644
> --- a/scripts/tracetool/__init__.py
> +++ b/scripts/tracetool/__init__.py
> @@ -140,8 +140,8 @@ class Event(object):
> The format strings for each argument.
> """
>
> - _CRE = re.compile("((?P<props>.*)\s+)?"
> - "(?P<name>[^(\s]+)"
> + _CRE = re.compile("((?P<props>[\w\s]+)\s+)?"
> + "(?P<name>\w+)"
> "\((?P<args>[^)]*)\)"
> "\s*"
> "(?:(?:(?P<fmt_trans>\".+),)?\s*(?P<fmt>\".+))?"
>
prev parent reply other threads:[~2014-09-30 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 10:37 [Qemu-devel] [PATCH v2] trace: tighten up trace-events regex to fix bad parse Stefan Hajnoczi
2014-09-24 13:39 ` Stefan Hajnoczi
2014-09-30 6:32 ` Eric Auger [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=542A4E9A.5010600@linaro.org \
--to=eric.auger@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vilanova@ac.upc.edu \
/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).