From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH] trace: update qemu-trace-stap to Python 3
Date: Tue, 7 Jan 2020 11:50:20 +0000 [thread overview]
Message-ID: <20200107115020.GZ3368802@redhat.com> (raw)
In-Reply-To: <20200107112438.383958-1-stefanha@redhat.com>
On Tue, Jan 07, 2020 at 11:24:38AM +0000, Stefan Hajnoczi wrote:
> qemu-trace-stap does not support Python 3 yet:
>
> $ scripts/qemu-trace-stap list path/to/qemu-system-x86_64
> Traceback (most recent call last):
> File "scripts/qemu-trace-stap", line 175, in <module>
> main()
> File "scripts/qemu-trace-stap", line 171, in main
> args.func(args)
> File "scripts/qemu-trace-stap", line 118, in cmd_list
> print_probes(args.verbose, "*")
> File "scripts/qemu-trace-stap", line 114, in print_probes
> if line.startswith(prefix):
> TypeError: startswith first arg must be bytes or a tuple of bytes, not str
>
> Now that QEMU requires Python 3.5 or later we can switch to pure Python
> 3. Use Popen()'s universal_newlines=True argument to treat stdout as
> text instead of binary.
>
> Fixes: 62dd1048c0bd ("trace: add ability to do simple printf logging via systemtap")
> Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1787395
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> scripts/qemu-trace-stap | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-01-07 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 11:24 [PATCH] trace: update qemu-trace-stap to Python 3 Stefan Hajnoczi
2020-01-07 11:50 ` Daniel P. Berrangé [this message]
2020-01-07 12:19 ` no-reply
2020-01-07 17:01 ` Stefan Hajnoczi
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=20200107115020.GZ3368802@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@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).