From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/28285] Allow stapbpf backend to handle $arg1, $arg2, ...
Date: Thu, 02 Sep 2021 19:23:59 +0000 [thread overview]
Message-ID: <bug-28285-6586-rPVMvT60gD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28285-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28285
--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
The issue is occuring because tapsets.cxx is writing the code for the access to
the argument in tapsets.cxx
sdt_uprobe_var_expanding_visitor::try_parse_arg_register around line 7053.
Later on the bpf-translate.cxx has no way of converting that magic string
containing the code to access an SDT marker argument into bpf.
There is similar generation of strings containing code in the following sdt
methods:
sdt_uprobe_var_expanding_visitor::try_parse_arg_register (target_symbol *e,
const string& asmarg,
long precision)
sdt_uprobe_var_expanding_visitor::try_parse_arg_offset_register (target_symbol
*e,
const string&
asmarg,
long
precision)
sdt_uprobe_var_expanding_visitor::try_parse_arg_effective_addr (target_symbol
*e,
const string&
asmarg,
long precision)
sdt_uprobe_var_expanding_visitor::try_parse_arg_varname (target_symbol *e,
const string& asmarg,
long precision)
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2021-09-02 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 19:50 [Bug bpf/28285] New: " wcohen at redhat dot com
2021-09-02 19:23 ` wcohen 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-28285-6586-rPVMvT60gD@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).