From: "gmoreira at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/23874] New: MIPS - semantic error: No cfa_ops supplied, but needed by DW_OP_call_frame_cfa
Date: Fri, 09 Nov 2018 05:09:00 -0000 [thread overview]
Message-ID: <bug-23874-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=23874
Bug ID: 23874
Summary: MIPS - semantic error: No cfa_ops supplied, but needed
by DW_OP_call_frame_cfa
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: gmoreira at gmail dot com
Target Milestone: ---
Created attachment 11388
--> https://sourceware.org/bugzilla/attachment.cgi?id=11388&action=edit
stap_report output
$ sudo stap --vp 01 -e 'probe kernel.function("do_truncate").return {
printf("filename '%s' \n", fullpath_struct_file(task_current(), @entry($filp)))
}'
semantic error: while processing probe
kernel.function("do_truncate@fs/open.c:37").return from:
kernel.function("do_truncate").return
semantic error: No cfa_ops supplied, but needed by DW_OP_call_frame_cfa:
identifier '$filp' at <input>:1:116
source: probe kernel.function("do_truncate").return { printf("filename
%s \n", fullpath_struct_file(task_current(), @entry($filp))) }
^
Pass 2: analyzed script: 2 probes, 45 functions, 4 embeds, 2 globals using
112704virt/89956res/4420shr/94964data kb, in 45930usr/4270sys/104142real ms.
Pass 2: analysis failed. [man error::pass2]
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-11-09 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 5:09 gmoreira at gmail dot com [this message]
2023-11-29 16:31 ` [Bug tapsets/23874] " 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-23874-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).