From: Steven Rostedt <rostedt@goodmis.org>
To: Sean Anderson <sean.anderson@linux.dev>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] Print arrays like Linux does
Date: Mon, 20 Oct 2025 13:35:05 -0400 [thread overview]
Message-ID: <20251020133505.48512dff@gandalf.local.home> (raw)
In-Reply-To: <b2c14f3a-b023-4688-9198-1f9b3e71320f@linux.dev>
On Mon, 20 Oct 2025 12:17:05 -0400
Sean Anderson <sean.anderson@linux.dev> wrote:
> On 8/26/24 17:00, Sean Anderson wrote:
> > In Linux, trace_print_array_seq prints array elements as hexadecimal
> > numbers, separates them with commas, and surrounds the whole thing with
> > curly braces. Modify print_str_arg to use the same formatting.
> >
> > Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
> > ---
> >
> > src/event-parse.c | 12 +++++++-----
> > 1 file changed, 7 insertions(+), 5 deletions(-)
> >
> > diff --git a/src/event-parse.c b/src/event-parse.c
> > index ba4a153..3c6f6f2 100644
> > --- a/src/event-parse.c
> > +++ b/src/event-parse.c
> > @@ -4938,18 +4938,19 @@ static void print_str_arg(struct trace_seq *s, void *data, int size,
> > len = eval_num_arg(data, size, event, arg->int_array.count);
> > el_size = eval_num_arg(data, size, event,
> > arg->int_array.el_size);
> > + trace_seq_putc(s, '{');
> > for (i = 0; i < len; i++) {
> > if (i)
> > - trace_seq_putc(s, ' ');
> > + trace_seq_putc(s, ',');
> >
> > if (el_size == 1) {
> > - trace_seq_printf(s, "%u", *(uint8_t *)num);
> > + trace_seq_printf(s, "0x%x", *(uint8_t *)num);
> > } else if (el_size == 2) {
> > - trace_seq_printf(s, "%u", *(uint16_t *)num);
> > + trace_seq_printf(s, "0x%x", *(uint16_t *)num);
> > } else if (el_size == 4) {
> > - trace_seq_printf(s, "%u", *(uint32_t *)num);
> > + trace_seq_printf(s, "0x%x", *(uint32_t *)num);
> > } else if (el_size == 8) {
> > - trace_seq_printf(s, "%"PRIu64, *(uint64_t *)num);
> > + trace_seq_printf(s, "0x%"PRIx64, *(uint64_t *)num);
> > } else {
> > trace_seq_printf(s, "BAD SIZE:%d 0x%x",
> > el_size, *(uint8_t *)num);
> > @@ -4958,6 +4959,7 @@ static void print_str_arg(struct trace_seq *s, void *data, int size,
> >
> > num += el_size;
> > }
> > + trace_seq_putc(s, '}');
> > break;
> > }
> > case TEP_PRINT_TYPE:
>
> ping
It's been accepted:
https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/commit/?id=5f570de85c6b6a391c5e7ffea0b9a54fd8c4b043
I just haven't had time to make a new official release.
-- Steve
next prev parent reply other threads:[~2025-10-20 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 21:00 [PATCH] Print arrays like Linux does Sean Anderson
2025-10-20 16:17 ` Sean Anderson
2025-10-20 17:35 ` Steven Rostedt [this message]
2025-10-20 17:38 ` Sean Anderson
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=20251020133505.48512dff@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=sean.anderson@linux.dev \
/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 NNTP newsgroup(s).