From: Sean Anderson <sean.anderson@linux.dev>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] Print arrays like Linux does
Date: Mon, 20 Oct 2025 13:38:18 -0400 [thread overview]
Message-ID: <5c01b127-686b-4890-aa79-810d159a6724@linux.dev> (raw)
In-Reply-To: <20251020133505.48512dff@gandalf.local.home>
On 10/20/25 13:35, Steven Rostedt wrote:
> 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
Great thanks. Just wanted to make sure this didn't get lost.
--Sean
prev parent reply other threads:[~2025-10-20 17:38 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
2025-10-20 17:38 ` Sean Anderson [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=5c01b127-686b-4890-aa79-810d159a6724@linux.dev \
--to=sean.anderson@linux.dev \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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 NNTP newsgroup(s).