From: Eugene Loh <eugene.loh@oracle.com>
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH] dtprobed: handle multiple providers in a single piece of DOF
Date: Thu, 14 Nov 2024 21:42:12 -0500 [thread overview]
Message-ID: <42969f56-3447-b869-c9f4-8a09fce59780@oracle.com> (raw)
In-Reply-To: <8ec502f1-47cf-812c-8b8a-3258b1a7caee@oracle.com>
I'm losing track of versions, but at some point I think your patch fixed
the (same) problem with a different script I was trying:
$ cat x.d
#pragma D attributes Evolving/Evolving/Common provider myprov provider
#pragma D attributes Private/Private/Unknown provider myprov module
#pragma D attributes Private/Private/Unknown provider myprov function
#pragma D attributes Evolving/Evolving/Common provider myprov name
#pragma D attributes Evolving/Evolving/Common provider myprov args
provider myprov
{
probe entry();
};
$ build/run-dtrace -h -s x.d
I had been getting a segfault (like you). Now it's simply:
dtrace: failed to compile script x.d: line 5: unused #pragma attributes
next prev parent reply other threads:[~2024-11-15 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 16:03 [PATCH] dtprobed: handle multiple providers in a single piece of DOF Nick Alcock
2024-11-14 19:53 ` Eugene Loh
2024-11-14 20:38 ` Nick Alcock
2024-11-14 21:25 ` Eugene Loh
2024-11-15 2:42 ` Eugene Loh [this message]
2024-11-15 20:55 ` 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=42969f56-3447-b869-c9f4-8a09fce59780@oracle.com \
--to=eugene.loh@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.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