public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH] utils: add args output to showUSDT.c
Date: Fri, 01 Nov 2024 15:27:52 +0000	[thread overview]
Message-ID: <878qu3km87.fsf@esperi.org.uk> (raw)
In-Reply-To: <ZyTyQuIOTB_zRDtC@kvh-deb-bpf.us.oracle.com> (Kris Van Hees via DTrace-devel's message of "Fri, 1 Nov 2024 11:22:42 -0400")

On 1 Nov 2024, Kris Van Hees via DTrace-devel verbalised:

> The showUSDT utility now reports argument type (native and translated)
> and mapping data for probes.
>
> Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>

Nice! Dropped my corresponding one.

Reviewed-by: Nick Alcock <nick.alcock@oracle.com>

One caveat:

>      printf("      Probe %d: %s:%s:%s:%s\n",
>  	   id, name, "",
>  	   strtab + probe->dofpr_func, strtab + probe->dofpr_name);
>      printf("        argc %d noffs %d nenoffs %d\n",
> -	   probe->dofpr_nargc, probe->dofpr_noffs, probe->dofpr_nenoffs);
> +	   probe->dofpr_xargc, probe->dofpr_noffs, probe->dofpr_nenoffs);

I think you shuld still print dofpr_nargc here too, because if it's
wrong we don't want the loop beyond to overrun and crash without any
previous indication of why :)

-- 
NULL && (void)

      reply	other threads:[~2024-11-01 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 15:22 [PATCH] utils: add args output to showUSDT.c Kris Van Hees
2024-11-01 15:27 ` Nick Alcock [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=878qu3km87.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=dtrace@lists.linux.dev \
    --cc=kris.van.hees@oracle.com \
    /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