From: Kris Van Hees <kris.van.hees@oracle.com>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH 2/3] usdt parser: handle encoded hyphens
Date: Mon, 30 Jun 2025 19:07:56 -0400 [thread overview]
Message-ID: <aGMYzHUs5f30mNnP@oracle.com> (raw)
In-Reply-To: <2a9a08cf-8261-e09a-abf4-0a3eb0f8db80@oracle.com>
On Mon, Jun 30, 2025 at 05:53:04PM -0400, Eugene Loh via DTrace-devel wrote:
> I would expect a patch like this to have a test to checks the behavior.
It does not need one because we already have one:
test/unittest/usdt/tst.entryreturn.sh
thoug that test does not quite pass yet due to other issues (still xfail).
But that test no longer causes the parser to complain that it cannot find
the probe (and abort). If you prefer I can certainly add a test for this
bug explicitly, though it essentially be quite similar to this case, but
it would be able to capture whether we encounter the parsing error or not
I think, so possible if preferred. But the test mentioned above certainly
cannot ever pass without this patch.
> On 6/24/25 17:40, Kris Van Hees via DTrace-devel wrote:
> > Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
> > ---
> > libcommon/usdt_parser_notes.c | 17 +++++++++++++++++
> > 1 file changed, 17 insertions(+)
> >
> > diff --git a/libcommon/usdt_parser_notes.c b/libcommon/usdt_parser_notes.c
> > index fb57f119..d3d744fb 100644
> > --- a/libcommon/usdt_parser_notes.c
> > +++ b/libcommon/usdt_parser_notes.c
> > @@ -471,6 +471,23 @@ parse_usdt_note(int out, dof_helper_t *dhp, usdt_data_t *data,
> > }
> > prbt.off = off;
> > + /*
> > + * If the probe name has encoded hyphens, perform in-place changing
> > + * from "__" into "-".
> > + */
> > + if (strstr(prbt.prb, "__") != NULL) {
> > + char *q;
> > + const char *s = prbt.prb, *e = p;
> > +
> > + for (q = (char *)s; s < e; s++, q++) {
> > + if (s[0] == '_' && s[1] == '_') {
> > + *q = '-';
> > + s++;
> > + } else if (s > q)
> > + *q = *s;
> > + }
> > + }
> > +
> > if ((prp = dt_htab_lookup(prbmap, &prbt)) == NULL) {
> > if ((prp = malloc(sizeof(dt_probe_t))) == NULL) {
> > usdt_error(out, ENOMEM, "Failed to allocate probe");
>
> _______________________________________________
> DTrace-devel mailing list
> DTrace-devel@oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/dtrace-devel
next prev parent reply other threads:[~2025-06-30 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 21:40 [PATCH 2/3] usdt parser: handle encoded hyphens Kris Van Hees
2025-06-30 21:53 ` [DTrace-devel] " Eugene Loh
2025-06-30 23:07 ` Kris Van Hees [this message]
2025-07-15 14:21 ` Nick Alcock
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=aGMYzHUs5f30mNnP@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@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