From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/26152] _struct_compat_timex_u() function doesn't work on rhel8
Date: Wed, 04 Oct 2023 14:30:49 +0000 [thread overview]
Message-ID: <bug-26152-6586-Sk6fCxczvM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26152-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26152
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
This works on current RHEL8 kernels with systemtap git commit ca71442b9
[wcohen@rhel8 systemtap]$ uname -a
Linux rhel8 4.18.0-514.el8.x86_64 #1 SMP Tue Sep 19 10:07:12 EDT 2023 x86_64
x86_64 x86_64 GNU/Linux
[wcohen@rhel8 systemtap]$ ../install/bin/stap -V
Systemtap translator/driver (version 5.0/0.189, release-4.8-147-gca71442b)
Copyright (C) 2005-2023 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.32 ... 6.5
enabled features: AVAHI BOOST_STRING_REF DYNINST BPF JAVA PYTHON2 PYTHON3
LIBRPM LIBSQLITE3 LIBVIRT LIBXML2 NLS NSS READLINE MONITOR_LIBS JSON_C
[wcohen@rhel8 systemtap]$ ../install/bin/stap -p4 -e 'probe
syscall.clock_adjtime {printf("%s\n", tx_uaddr_str)}'
/home/wcohen/.systemtap/cache/a0/stap_a0317735832db1578751089e63f33b99_70663.ko
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2023-10-04 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 18:45 [Bug tapsets/26152] New: " wcohen at redhat dot com
2020-06-29 15:39 ` [Bug tapsets/26152] " wcohen at redhat dot com
2023-10-04 14:30 ` 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-26152-6586-Sk6fCxczvM@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).