From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] trace: Fix 'char **' compilation error in simple backend
Date: Tue, 25 Oct 2016 21:29:16 -0500 [thread overview]
Message-ID: <0137c2f9-8e21-1269-8c60-f33dd8850ca9@redhat.com> (raw)
In-Reply-To: <1477447172-19677-1-git-send-email-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1771 bytes --]
On 10/25/2016 08:59 PM, Fam Zheng wrote:
> Currently, the generated function body will do "strlen(arg)" but the
> argument could be 'char **'. Avoid that by exclusding such cases in
s/exclusding/excluding/
> is_string check.
>
> Reported by patchew's "make docker-test-mingw@fedora".
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> scripts/tracetool/backend/simple.py | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/tracetool/backend/simple.py b/scripts/tracetool/backend/simple.py
> index 9885e83..2538795 100644
> --- a/scripts/tracetool/backend/simple.py
> +++ b/scripts/tracetool/backend/simple.py
> @@ -21,7 +21,9 @@ PUBLIC = True
>
> def is_string(arg):
> strtype = ('const char*', 'char*', 'const char *', 'char *')
> - if arg.lstrip().startswith(strtype):
> + non_strtype = ('const char**', 'char**', 'const char **', 'char **')
> + arg_strip = arg.lstrip()
> + if arg_strip.startswith(strtype) and not arg_strip.startswith(non_strtype):
There may be a more compact way to write it, but I'm not enough of a
python expert to know offhand what else to suggest (it's not as simple
as string concatenation of strtype + '*', since strtype is a tuple
rather than a string).
What you have will fail to detect 'const char *const *' as a non-string
(possible if we have some argv-like function that takes a constant array
of constant strings), but I guess we can worry about that if we actually
try to trace something with that signature. In the meantime, what you
have solves the immediate failure, so:
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-10-26 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 1:59 [Qemu-devel] [PATCH] trace: Fix 'char **' compilation error in simple backend Fam Zheng
2016-10-26 2:29 ` Eric Blake [this message]
2016-10-26 2:46 ` Fam Zheng
2016-10-26 2:56 ` Eric Blake
2016-10-26 3:05 ` Fam Zheng
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=0137c2f9-8e21-1269-8c60-f33dd8850ca9@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).