From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/29756] New: stap -L regexp match broken on some arches
Date: Mon, 07 Nov 2022 10:35:37 +0000 [thread overview]
Message-ID: <bug-29756-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29756
Bug ID: 29756
Summary: stap -L regexp match broken on some arches
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: ---
On some arches (interestingly, this only seems to be a problem on ppc64le and
s390x, but not on x86_64 or aarch64) the stap -L regexp match doesn't work for
a function name in case the source file isn't specified. If the source file is
specified (a base name without any kind of path is good enough) then the match
works fine. Details:
9 ppc64le # stap -L 'process("/lib64/libc.so.6").function("malloc_init_state")'
9 ppc64le # stap -L
'process("/lib64/libc.so.6").function("malloc_init_state*")'
process("/usr/lib64/libc.so.6").function("malloc_init_state@/usr/src/debug/glibc-2.34-48.el9.ppc64le/malloc/malloc.c:1932")
$av:mstate
9 ppc64le # stap -L
'process("/lib64/libc.so.6").function("malloc_init_state@/usr/src/debug/glibc-2.34-48.el9.ppc64le/malloc/malloc.c")'
process("/usr/lib64/libc.so.6").function("malloc_init_state@/usr/src/debug/glibc-2.34-48.el9.ppc64le/malloc/malloc.c:1932")
$av:mstate
9 ppc64le # stap -L
'process("/lib64/libc.so.6").function("malloc_init_state@malloc.c")'
process("/usr/lib64/libc.so.6").function("malloc_init_state@/usr/src/debug/glibc-2.34-48.el9.ppc64le/malloc/malloc.c:1932")
$av:mstate
9 ppc64le # stap -L 'process("/lib64/libc.so.6").function("malloc_init_state")'
9 ppc64le #
This is with kernel 5.14.0-186.kpq1.el9.ppc64le and stap upstream commit
e51e989e33b0f0a0cf26d00755340cef3c2ea81f .
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-11-07 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 10:35 mcermak at redhat dot com [this message]
2023-10-12 20:16 ` [Bug runtime/29756] " wcohen at redhat dot com
2023-10-13 19:24 ` wcohen at redhat dot com
2023-10-16 19:58 ` [Bug translator/29756] " 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-29756-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).