From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30534] program received "Illegal instruction" when using systemtap set a probe and hit the probe
Date: Thu, 12 Oct 2023 20:43:57 +0000 [thread overview]
Message-ID: <bug-30534-6586-mL962ufj4c@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30534-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30534
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
CC| |wcohen at redhat dot com
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
As the upstream systemtap doesn't currently build on RHEL7 because of missing
debuginfod support in elfutils resorted to trying things with the existing
systemtap available in RHEL7.9. Things appeared to work correctly:
[root@hpe-dl160gen8-01 ~]# rpm -q kernel glibc systemtap
kernel-3.10.0-1160.el7.x86_64
glibc-2.17-317.el7.x86_64
glibc-2.17-317.el7.i686
systemtap-4.0-13.el7.x86_64
[root@hpe-dl160gen8-01 ~]# stap dbg-core.stp -c /usr/bin/ls
anaconda-ks.cfg NETBOOT_METHOD.TXT rpmbuild
dbg-core.stp original-ks.cfg systemtap-5.0-1.el8.src.rpm
dbg-core.stp~ RECIPE.TXT systemtap_write
call _IO_new_fclose()call _IO_new_fclose()[root@hpe-dl160gen8-01 ~]# cat
dbg-core.stp
probe process("/lib64/libc.so.6").function("_IO_new_fclose").return
{
printf ("call _IO_new_fclose()")
}
The only difference I can see is that this is the kernel is a bit newer.
Doesn't look like we are able to replicate this.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2023-10-12 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 14:39 [Bug runtime/30534] New: " yang.pan@nokia-sbell.com
2023-10-12 20:43 ` 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-30534-6586-mL962ufj4c@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).