Date: Mon, 2 Mar 2020 23:25:11 +0530 From: Kamal Prasad <kamalpr@gmail.com> To: Mark Johnston <markj@freebsd.org> Cc: freebsd-dtrace@freebsd.org Subject: Re: set argument Message-ID: <195BCF76-F75E-49D3-A5F6-3D3A8DE28206@gmail.com> In-Reply-To: <20200302172752.GD26104@spy> References: <CAK=yUGL8Ls5V4E=ucPJ9Unvf_UhDDngU7ue%2BkeRL3Zx2khJw5Q@mail.gmail.com> <20200302161350.GB26104@spy> <2D6C721A-C868-4D4F-90CD-9D57BC783ADF@gmail.com> <20200302172752.GD26104@spy>
next in thread | previous in thread | raw e-mail | index | archive | help
There are some headers which are not getting picked up e.g.:- if.h on =
arm.
Even otherwise, if I set WITH_CTF=3DYES, will include a proprietary =
header file automatically? You might be having a list somewhere to =
specify on which files ctfconvert is run when building the kernel.
> On Mar 2, 2020, at 10:57 PM, Mark Johnston <markj@freebsd.org> wrote:
>=20
> On Mon, Mar 02, 2020 at 10:32:31PM +0530, Kamal Prasad wrote:
>> In userspace. Where do you provide information so that dtrace can =
automatically see sys/net/route.h structs like struct rtentry?
>> I want to add some more files so that their structs are also =
automatically seen by dtrace.
>=20
> Currently this is done by running ctfconvert on each object file, and =
by
> running ctfmerge on the output file (usually an executable or shared
> lib) of the build. If you're using FreeBSD's build infrastructure it
> should be sufficient to just set WITH_CTF=3DYES.
>=20
>>> On Mar 2, 2020, at 9:43 PM, Mark Johnston <markj@freebsd.org> wrote:
>>>=20
>>> On Mon, Mar 02, 2020 at 03:33:57PM +0530, Kamal R. Prasad wrote:
>>>> hello,
>>>>=20
>>>> How does dtrace access the argument type declarations when we =
define a new
>>>> SDT? eg:- I define an SDT that has arg0 as (struct mystrust*)
>>>>=20
>>>> I have defined in my proprietary header file
>>>> ---------------
>>>> typedef struct abc {
>>>> int a;
>>>> int b;
>>>> int c;
>>>> };
>>>> typedef struct def {
>>>> int d;
>>>> int e;
>>>> int f;
>>>> };
>>>>=20
>>>> typedef struct mystrust {
>>>> struct abc* myarg1;
>>>> struct def* myarg2
>>>> };
>>>> ---------------
>>>>=20
>>>> I want my probe to be able to access the typedeffor struct abc and =
struct
>>>> def.
>>>=20
>>> Is this in the kernel or userspace? We automatically build the =
kernel
>>> with CTF info included, so dtrace should be able to see the =
structure
>>> definitions automatically.
>>> _______________________________________________
>>> freebsd-dtrace@freebsd.org <mailto:freebsd-dtrace@freebsd.org> =
<mailto:freebsd-dtrace@freebsd.org <mailto:freebsd-dtrace@freebsd.org>> =
mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace =
<https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace><https://lists.=
freebsd.org/mailman/listinfo/freebsd-dtrace =
<https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace>>;
>>> To unsubscribe, send any mail to =
"freebsd-dtrace-unsubscribe@freebsd.org =
<mailto:freebsd-dtrace-unsubscribe@freebsd.org> =
<mailto:freebsd-dtrace-unsubscribe@freebsd.org =
<mailto:freebsd-dtrace-unsubscribe@freebsd.org>>"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?195BCF76-F75E-49D3-A5F6-3D3A8DE28206>