Messages in this thread | | | From | Chuck Lever III <> | Subject | Re: possible trace_printk() bug in v5.19-rc1 | Date | Mon, 27 Jun 2022 15:51:04 +0000 |
| |
> On Jun 27, 2022, at 11:43 AM, Steven Rostedt <rostedt@goodmis.org> wrote: > > On Sun, 26 Jun 2022 17:09:31 +0000 > Chuck Lever III <chuck.lever@oracle.com> wrote: > >> [cel@manet lib]$ cd /usr/lib64/ >> [cel@manet lib64]$ ls libtrace* >> libtracecmd.so.1 libtracecmd.so.1.0.0 libtraceevent.so.1 libtraceevent.so.1.2.1 libtracefs.so.1 libtracefs.so.1.1.1 >> [cel@manet lib64]$ > > According to https://trace-cmd.org > > The latest libraries are: > > libtraceevent 1.6.1 > libtracefs 1.4.1 > > I'm guessing you may have a buggy version.
I checked with dnf. I have the latest versions provided in Fedora 35, which is still supported.
I'd like to avoid having to maintain the latest version of the tool and its libraries by hand on all of my development systems.
-- Chuck Lever
| |