set argument

[Kamal Prasad]

There are some headers which are not getting picked up e.g.:- if.h on arm.
Even otherwise, if I set WITH_CTF=YES, 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 at freebsd.org> wrote:
> 
> 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.
> 
> 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=YES.
> 
>>> On Mar 2, 2020, at 9:43 PM, Mark Johnston <markj at freebsd.org> wrote:
>>> 
>>> On Mon, Mar 02, 2020 at 03:33:57PM +0530, Kamal R. Prasad wrote:
>>>> hello,
>>>> 
>>>> 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*)
>>>> 
>>>> 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;
>>>> };
>>>> 
>>>> typedef struct mystrust {
>>>> struct abc* myarg1;
>>>> struct def* myarg2
>>>> };
>>>> ---------------
>>>> 
>>>> I want my probe to be able to access the typedeffor struct abc and struct
>>>> def.
>>> 
>>> 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 at freebsd.org <mailto:freebsd-dtrace at freebsd.org> <mailto:freebsd-dtrace at freebsd.org <mailto:freebsd-dtrace at 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 at freebsd.org <mailto:freebsd-dtrace-unsubscribe at freebsd.org> <mailto:freebsd-dtrace-unsubscribe at freebsd.org <mailto:freebsd-dtrace-unsubscribe at freebsd.org>>"