From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/29756] stap -L regexp match broken on some arches
Date: Mon, 16 Oct 2023 19:58:35 +0000 [thread overview]
Message-ID: <bug-29756-6586-iwjPcNWtgT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29756-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29756
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|runtime |translator
--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
This looks like an issue with systemtap understanding the debuginfo generated
as part of the rpmbuild process. When locally building the
glibc-2.34-83.el9_3.7.src.rpm on the machine the following work fine on the
unstripped glibc.so.6:
[root@s390x-kvm-033 build-s390x-redhat-linux]#
~/systemtap_write/install/bin/stap -v -L
'process("./libc.so.6").function("malloc_init_state")'
Pass 1: parsed user script and 489 library scripts using
127764virt/106232res/10972shr/94700data kb, in 230usr/30sys/256real ms.
process("/root/rpmbuild/BUILD/glibc-2.34/build-s390x-redhat-linux/libc.so").function("malloc_init_state@/root/rpmbuild/BUILD/glibc-2.34/malloc/malloc.c:1932")
/* pc=.dynamic+0xab576 */ $av:mstate
process("/root/rpmbuild/BUILD/glibc-2.34/build-s390x-redhat-linux/libc.so").function("malloc_init_state@/root/rpmbuild/BUILD/glibc-2.34/malloc/malloc.c:1932")
/* pc=.dynamic+0xab9e0 */ $av:mstate
Pass 2: analyzed script: 2 probes, 0 functions, 0 embeds, 0 globals using
137564virt/117272res/12220shr/104500data kb, in 50usr/0sys/57real ms.
However, install the rpms created from that same build a wildcard is needed to
find malloc_init_state:
#cd rpmbuild/RPMS/s390x/
#dnf install -y ./glibc-gconv-extra-2.34-83.el9.7.s390x.rpm
./glibc-langpack-en-2.34-83.el9.7.s390x.rpm
./glibc-common-2.34-83.el9.7.s390x.rpm ./glibc-2.34-83.el9.7.s390x.rpm
./glibc-headers-2.34-83.el9.7.s390x.rpm ./glibc-devel-2.34-83.el9.7.s390x.rpm
./glibc-debugsource-2.34-83.el9.7.s390x.rpm
./glibc-debuginfo-2.34-83.el9.7.s390x.rpm
./glibc-static-2.34-83.el9.7.s390x.rpm
# ~/systemtap_write/install/bin/stap -v -L
'process("/lib64/libc.so.6").function("malloc_init_state")'
Pass 1: parsed user script and 489 library scripts using
127764virt/106232res/10972shr/94700data kb, in 230usr/30sys/259real ms.
Pass 2: analyzed script: 0 probes, 0 functions, 0 embeds, 0 globals using
151728virt/131664res/12412shr/118664data kb, in 100usr/0sys/113real ms.
# ~/systemtap_write/install/bin/stap -v -L
'process("/lib64/libc.so.6").function("malloc_init_state*")'
Pass 1: parsed user script and 489 library scripts using
127768virt/106236res/10972shr/94704data kb, in 240usr/30sys/254real ms.
process("/usr/lib64/libc.so.6").function("malloc_init_state@/usr/src/debug/glibc-2.34-83.el9.7.s390x/malloc/malloc.c:1932")
/* pc=.dynamic+0xab576 */ $av:mstate $tcache:tcache_perthread_struct*
process("/usr/lib64/libc.so.6").function("malloc_init_state@/usr/src/debug/glibc-2.34-83.el9.7.s390x/malloc/malloc.c:1932")
/* pc=.dynamic+0xab9e0 */ $av:mstate $tcache:tcache_perthread_struct*
Pass 2: analyzed script: 2 probes, 0 functions, 0 embeds, 0 globals using
151820virt/131536res/12220shr/118756data kb, in 110usr/0sys/120real ms.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2023-10-16 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 10:35 [Bug runtime/29756] New: " mcermak at redhat dot com
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 ` wcohen at redhat dot com [this message]
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-iwjPcNWtgT@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).