From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] trace: avoid SystemTap "char const" warnings
Date: Thu, 1 Feb 2018 17:20:39 +0000 [thread overview]
Message-ID: <20180201172039.GD5578@stefanha-x1.localdomain> (raw)
In-Reply-To: <20180201162625.4276-1-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
On Thu, Feb 01, 2018 at 04:26:25PM +0000, Stefan Hajnoczi wrote:
> SystemTap's dtrace(1) produces the following warning when it encounters
> "char const" instead of "const char":
>
> Warning: /usr/bin/dtrace:trace-dtrace-root.dtrace:66: syntax error near:
> probe flatview_destroy_rcu
>
> Warning: Proceeding as if --no-pyparsing was given.
>
> This is a limitation in current SystemTap releases. I have sent a patch
> upstream to accept "char const" since it is valid C:
>
> https://sourceware.org/ml/systemtap/2018-q1/msg00017.html
>
> In QEMU we still wish to avoid warnings in the current SystemTap
> release. It's simple enough to replace "char const" with "const char".
>
> I'm not changing the documentation or implementing checks to prevent
> this from occurring again in the future. The next release of SystemTap
> will hopefully resolve this issue.
>
> Cc: Daniel P. Berrange <berrange@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> hw/block/trace-events | 4 ++--
> trace-events | 12 ++++++------
> 2 files changed, 8 insertions(+), 8 deletions(-)
Thanks, applied to my tracing tree:
https://github.com/stefanha/qemu/commits/tracing
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2018-02-01 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 16:26 [Qemu-devel] [PATCH] trace: avoid SystemTap "char const" warnings Stefan Hajnoczi
2018-02-01 16:27 ` Daniel P. Berrangé
2018-02-01 17:02 ` Philippe Mathieu-Daudé
2018-02-01 17:20 ` 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=20180201172039.GD5578@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--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).