[dtrace-discuss] Beginners question on providers

2010-03-15 Thread Paul Johnston
Hi If I list all the providers I see a list for apache like below: apache3156 apache3164 apache3165 apache3167 apache3168 apache3509 apache7363 apache7364 apache7365 apache7366 apache7367 Why do I see so many and what are their differences. Best Regards Paul -- This message posted from

Re: [dtrace-discuss] Beginners question on providers

2010-03-15 Thread Mads Toftum
On Mon, Mar 15, 2010 at 03:24:17AM -0700, Paul Johnston wrote: Hi If I list all the providers I see a list for apache like below: apache3156 apache3164 apache3165 apache3167 apache3168 apache3509 apache7363 apache7364 apache7365 apache7366 apache7367 Why do I see so many and what are

Re: [dtrace-discuss] Beginners question on providers

2010-03-15 Thread krishnan parthasarathi - Sun Microsystems - Bangalore India
Hi Paul, Apache has USDT probes (http://wikis.sun.com/display/DTrace/Statically+Defined+Tracing+for+User+Applications) defined in it. These are per-process and are unique to a running instance of Apache process. That explains why you see probes of the form apachepid:::. thanks, Krishnan On

Re: [dtrace-discuss] Need some help

2010-03-15 Thread James Carlson
On 03/15/10 08:20, tester wrote: fbt::door_call:entry /curpsinfo-pr_dmodel == PR_MODEL_LP64/ { printf(entry args are %lx and %lx \n, arg0, , *(uint64_t *)copyin(arg1, 8)); } Nico Thanks Nico. Since arg1 is a pointer to a struct in userland, can I use ptr = *(uint32_t *)copyin(arg1,

Re: [dtrace-discuss] Need some help

2010-03-15 Thread tester
I am getting a 64bit address for char pointer for a 32 bit process. I don't know if I am getting the casting correct. #!/usr/sbin/dtrace -qs typedef struct door_arg { char *data_ptr; /* Argument/result buf ptr*/ size_t data_size; /*

Re: [dtrace-discuss] Need some help

2010-03-15 Thread Nicolas Williams
On Mon, Mar 15, 2010 at 12:20:35PM -0700, tester wrote: #!/usr/sbin/dtrace -qs typedef struct door_arg { char *data_ptr; /* Argument/result buf ptr*/ size_t data_size; /* Argument/result buf size */ door_desc_t *desc_ptr;

Re: [dtrace-discuss] Need some help

2010-03-15 Thread tester
Thank you Michael and Nico. I will post my results after the test. Much appreciated. -- This message posted from opensolaris.org ___ dtrace-discuss mailing list dtrace-discuss@opensolaris.org

[dtrace-discuss] Slow start of Dtrace?

2010-03-15 Thread Henk Vandenbergh
have been playing with dtrace for the past week and besides some beginner errors I'm doing basically fine (thanks again Adam). I just switched to a different system, and all of a sudden it takes about 15 seconds for the dtrace script to start and then an other 6 seconds to terminate. System is