From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30987] New: Addition of strlcopy and strlcat to glibc prevents compilation of dyninst based systemtap instrumentation
Date: Fri, 20 Oct 2023 14:42:45 +0000 [thread overview]
Message-ID: <bug-30987-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30987
Bug ID: 30987
Summary: Addition of strlcopy and strlcat to glibc prevents
compilation of dyninst based systemtap instrumentation
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: wcohen at redhat dot com
Target Milestone: ---
On Fedora rawhide the systemtap "make installcheck" tests building
instrumentation using dyninst fail to compile because glibc has added strlcpy
and strlcat to the /usr/include/string.h file and those declarations conflict
with the static inlined functioned in runtime/dynsint/linux_defs.h. This is
causing over 400 failures on rawhide for the "make installcheck". Can
replicate with:
sudo make installcheck RUNTESTFLAGS="systemtap.base/ret-uprobe-var.exp"
And see following in the output:
FAIL: ret-uprobe-var: TEST 1: @var in return probes should not be stale (4.1+)
(dyninst): stderr: string should be "", but got "In file included from
/home/wcohen/systemtap_write/install/share/systemtap/runtime/dyninst/runtime.h:92,
from
/home/wcohen/systemtap_write/install/share/systemtap/runtime/runtime.h:30,
from
/tmp/stapDni8D1/stap_e18df6414ee02f320dd0e235e95dc3d9_2203_src.c:21:
/home/wcohen/systemtap_write/install/share/systemtap/runtime/dyninst/linux_defs.h:100:22:
error: static declaration of 'strlcpy' follows non-static declaration
100 | static inline size_t strlcpy(char *__restrict dest, const char
*__restrict src, size_t size)
| ^~~~~~~
In file included from
/home/wcohen/systemtap_write/install/share/systemtap/runtime/dyninst/runtime.h:22:
/usr/include/string.h:506:15: note: previous declaration of 'strlcpy' with type
'size_t(char * restrict, const char * restrict, size_t)' {aka 'long unsigned
int(char * restrict, const char * restrict, long unsigned int)'}
506 | extern size_t strlcpy (char *__restrict __dest,
| ^~~~~~~
/home/wcohen/systemtap_write/install/share/systemtap/runtime/dyninst/linux_defs.h:112:22:
error: static declaration of 'strlcat' follows non-static declaration
112 | static inline size_t strlcat(char *__restrict dest, const char
*__restrict src, size_t count)
| ^~~~~~~
/usr/include/string.h:512:15: note: previous declaration of 'strlcat' with type
'size_t(char * restrict, const char * restrict, size_t)' {aka 'long unsigned
int(char * restrict, const char * restrict, long unsigned int)'}
512 | extern size_t strlcat (char *__restrict __dest,
| ^~~~~~~
WARNING: gcc exited with status: 1
Pass 4: compilation failed. [man error::pass4]
"
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-10-20 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 14:42 wcohen at redhat dot com [this message]
2023-10-24 18:15 ` [Bug runtime/30987] " wcohen at redhat dot com
2023-10-25 16:00 ` 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-30987-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).