From: "dgilbert at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/23634] WARNING: Can't parse SDT_V3 operand for x86_64 qemu tapset probe points
Date: Thu, 15 Apr 2021 15:46:58 +0000 [thread overview]
Message-ID: <bug-23634-6586-mpz6Ye0MT5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23634-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23634
Dr. David Alan Gilbert <dgilbert at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |dgilbert at redhat dot com
Resolution|WORKSFORME |---
--- Comment #6 from Dr. David Alan Gilbert <dgilbert at redhat dot com> ---
I'm seeing this here on RHEL8.4 qemu 5.2
probe qemu.kvm.ram_load_complete =
process("/usr/libexec/qemu-kvm").mark("ram_load_complete")
{
ret = $arg1;
seq_iter = $arg2;
}
# qemu-trace-stap -v run /usr/libexec/qemu-kvm 'mig*' '*vmstate*'
'*savevm*' 'bdrv*' 'blk*' 'qcow*' '*loadvm*' 'ram_*'
Using tapset dir '/usr/share/systemtap/tapset' for binary
'/usr/libexec/qemu-kvm'
Compiling script 'probe qemu.kvm.log.mig* {} probe qemu.kvm.log.*vmstate* {}
probe qemu.kvm.log.*savevm* {} probe qemu.kvm.log.bdrv* {} probe
qemu.kvm.log.blk* {} probe qemu.kvm.log.qcow* {} probe qemu.kvm.log.*loadvm* {}
probe qemu.kvm.log.ram_* {}'
WARNING: Can't parse SDT_V3 operand 'seq_iter.31484(%rip)' [man error::sdt]:
identifier '$arg2' at /usr/share/systemtap/tapset/qemu-kvm.stp:17906:14
source: seq_iter = $arg2;
^
WARNING: cannot find module /usr/libexec/qemu-kvm debuginfo: No DWARF
information found [man warning::debuginfo]
semantic error: debuginfo scope not found for module '/usr/libexec/qemu-kvm',
cannot resolve context variable [man error::dwarf]: identifier '$arg2' at
:17906:14
source: seq_iter = $arg2;
^
semantic error: debuginfo scope not found for module '/usr/libexec/qemu-kvm',
cannot resolve context variable [man error::dwarf]: identifier '$arg2' at
:17906:14
source: seq_iter = $arg2;
^
semantic error: SDT asm not understood, requires debuginfo [man error::sdt]:
identifier '$arg2' at :17906:14
source: seq_iter = $arg2;
^
Missing separate debuginfos, use: debuginfo-install
qemu-kvm-core-5.2.0-15.module+el8.4.0+10650+50781ca0.x86_64
Pass 2: analysis failed. [man error::pass2]
Number of similar warning messages suppressed: 1.
Rerun with -v to see them.
seq_iter here is a little odd; it's a local static.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-04-15 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 19:12 [Bug translator/23634] New: WARNING: Can't parse SDT_V3 operand for x86_64 qemu shared libraries wcohen at redhat dot com
2018-09-11 19:24 ` [Bug translator/23634] WARNING: Can't parse SDT_V3 operand for x86_64 qemu tapset probe points wcohen at redhat dot com
2018-09-12 14:03 ` wcohen at redhat dot com
2018-09-12 14:12 ` fche at redhat dot com
2018-09-12 15:03 ` wcohen at redhat dot com
2018-09-12 15:56 ` fche at redhat dot com
2020-02-19 21:07 ` fche at redhat dot com
2021-04-15 15:46 ` dgilbert at redhat dot com [this message]
2021-04-19 19:15 ` fche at redhat dot com
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=bug-23634-6586-mpz6Ye0MT5@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).