From: "fche 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: Mon, 19 Apr 2021 19:15:09 +0000 [thread overview]
Message-ID: <bug-23634-6586-rIUQ3T2biI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23634-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23634
--- Comment #7 from Frank Ch. Eigler <fche at redhat dot com> ---
For stap to make sense of such an operand, it'd have to decode symbol names
rather than register name / offset literal type constructs. Not only that, but
do so on a scope-sensitive basis to make sure the correct symbol is matched to
the name -- but that scope information is not available. Not sure how much we
can do.
I would suggest tweaking your stap_probe macro call to pass the given parameter
some way other than literally from that static var. Maybe add a number to it,
and then subtract it back out in the tapset?
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2021-04-19 19:15 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
2021-04-19 19:15 ` fche at redhat dot com [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=bug-23634-6586-rIUQ3T2biI@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).