On Mon, 04 Mar 2024 23:40:49 +0100 Tobias Waldekranz <tobias@xxxxxxxxxxxxxx> wrote: > On ons, feb 28, 2024 at 09:56, Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > On Wed, 28 Feb 2024 11:47:24 +0100 > > Tobias Waldekranz <tobias@xxxxxxxxxxxxxx> wrote: > > > > The "trace_seq p" is a pointer to trace_seq descriptor that can build > > strings, and then you can use it to print a custom string in the trace > > output. > > Yes I managed to decode the hidden variable :) I also found > trace_seq_acquire() (and its macro alter ego __get_buf()), which would > let me keep the generic stringer functions. So far, so good. > > I think the foundational problem remains though: TP_printk() is not > executed until a user reads from the trace_pipe; at which point the > object referenced by __entry->info may already be dead and > buried. Right? Correct. You would need to load all the information into the event data itself, at the time of the event is triggered, that is needed to determine how to display it. -- Steve
