From: "913495245 at qq dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/28334] New: cannot handle offset into register
Date: Mon, 13 Sep 2021 10:20:01 +0000 [thread overview]
Message-ID: <bug-28334-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28334
Bug ID: 28334
Summary: cannot handle offset into register
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: 913495245 at qq dot com
Target Milestone: ---
Hi team
I had a function trace demo with Struct parameter and Struct return, but got
the "cannot handle offset into register" error.
my environments:
os: Ubuntu 16.04 LTS
gcc 8.3
systemtap 4.5
elfutils 0.185
# func.h
struct DataPackage {
int len;
float width;
// float width2; // uncomment this line will work :)
double angle;
};
struct DataPackage func_complex_v2(struct DataPackage input_data, int page);
# func.c
struct DataPackage func_complex_v2(struct DataPackage input_data, int page) {
struct DataPackage d;
d.len = 19;
d.width = 115.33;
d.angle = 6.66;
return d;
}
# main.c
int main(int argc, char const *argv[])
{
struct DataPackage d;
d.len = 997;
d.width = 10;
d.angle = 0.777;
struct DataPackage r =func_complex_v2(d, 789);
return 0;
}
# cc_stap_test_complex.stp
probe
process("/home/xyz/vs_workspace/CacheLab/build/test").function("func_complex_v2").return
{
printf("func_complex_v2 return: %s\n", fp_to_string($return->width, 6))
}
Here is the console output:
Debug translate_offsetsemantic error: cannot handle offset into register:
identifier '$return' at
/home/xyz/cc_stap_test_complex.stp:73:57
source: printf("func_complex_v2 return: %s\n",
fp_to_string($return->width, 6))
^
semantic error: unresolved type : identifier '$return' at :73:57
source: printf("func_complex_v2 return: %s\n",
fp_to_string($return->width, 6))
Any advice is appreciate, thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-09-13 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 10:20 913495245 at qq dot com [this message]
2022-05-19 20:25 ` [Bug translator/28334] " scox at redhat dot com
2022-05-19 20:31 ` fche at redhat dot com
2022-05-19 20:50 ` scox at redhat dot com
2022-07-01 17:39 ` wcohen at redhat dot com
2022-07-01 17:44 ` wcohen 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-28334-6586@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).