From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/26379] New: stap -p4 systemtap.examples/network/nfsd-trace.stp fails
Date: Thu, 13 Aug 2020 06:50:57 +0000 [thread overview]
Message-ID: <bug-26379-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26379
Bug ID: 26379
Summary: stap -p4 systemtap.examples/network/nfsd-trace.stp
fails
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
Target Milestone: ---
# stap -w -p4
/usr/share/systemtap/testsuite/systemtap.examples/network/nfsd-trace.stp
/tmp/stapeavvoX/stap_25c36caa1999fbf6d530c1828a4a04f1_54669_src.c: In function
‘function___global_kernel_string__overload_0’:
/tmp/stapeavvoX/stap_25c36caa1999fbf6d530c1828a4a04f1_54669_src.c:11212:42:
error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument
4 has type ‘void *’ [-Werror=format=]
"kernel string copy fault at 0x%lx [man error::fault]", (void *)
~~^
%p
cc1: all warnings being treated as errors
make[1]: *** [scripts/Makefile.build:315:
/tmp/stapeavvoX/stap_25c36caa1999fbf6d530c1828a4a04f1_54669_src.o] Error 1
make: *** [Makefile:1545: _module_/tmp/stapeavvoX] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed. [man error::pass4]
#
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-08-13 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 6:50 mcermak at redhat dot com [this message]
2020-08-13 6:52 ` [Bug runtime/26379] " mcermak 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-26379-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).