From: "Philippe Mathieu-Daudé" <1844814@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1844814] Re: trace: SystemTap documentation out of date
Date: Mon, 16 Dec 2019 12:18:42 -0000 [thread overview]
Message-ID: <157649872273.18439.6864370970460927755.malone@wampee.canonical.com> (raw)
In-Reply-To: 156899381888.13411.12132927689585572811.malonedeb@gac.canonical.com
Fixed in v4.2.0.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1844814
Title:
trace: SystemTap documentation out of date
Status in QEMU:
Fix Released
Bug description:
The docs/devel/tracing.txt help suggest:
scripts/tracetool.py --backends=dtrace --format=stap \
--binary path/to/qemu-binary \
--target-type system \
--target-name x86_64 \
<trace-events-all >qemu.stp
but since commit 2098c56a9bc this comment is outdated:
$ scripts/tracetool.py --backends=dtrace --format=stap \
--binary mips-softmmu/qemu-system-mips \
--target-type system \
--target-name mips trace-events-all
Error: group name is required
The offending commit seems:
commit 2098c56a9bc5901e145fa5d4759f075808811685
Author: Daniel P. Berrange <berrange@redhat.com>
Date: Wed Jan 25 16:14:14 2017 +0000
trace: move setting of group name into Makefiles
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1844814/+subscriptions
prev parent reply other threads:[~2019-12-16 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 15:36 [Bug 1844814] [NEW] trace: SystemTap documentation out of date Philippe Mathieu-Daudé
2019-11-08 13:59 ` [Bug 1844814] " Philippe Mathieu-Daudé
2019-12-16 12:18 ` Philippe Mathieu-Daudé [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=157649872273.18439.6864370970460927755.malone@wampee.canonical.com \
--to=1844814@bugs.launchpad.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).