linux-kernel - Re: ftrace trace_raw

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191217185401.30824f2c@gandalf.local.home>
Date:   Tue, 17 Dec 2019 18:54:01 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     David Laight <David.Laight@...LAB.COM>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Sudip Mukherjee <sudipm.mukherjee@...il.com>
Subject: Re: ftrace trace_raw_pipe format

On Tue, 17 Dec 2019 18:36:41 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:

> Also note, once you are here, you don't need to use the
> tep_print_event() to print out the fields of record. You can also
> extract the data from the event directly. Or you could register a
> handler that will get called via the tep_print_event().

And of course, if you are unaware, trace-cmd does all this for you too:

 http://www.trace-cmd.org

;-)

-- Steve