Hi Hillel:
The second tuple in the pid probe definition is for the name of the library
and not the threadId.
You can do what want by using a predicate.
pid$target:a.out::entry
/tid=3/
{
put code here
}
HTHs
Angelo
On Dec 8, 2009, at 3:20 PM, Hillel (Sabba) Markowitz wrote:
> I have an application that generates threads during the process. I
> start it with
>
> pid$target:Base::entry
> {
> put code here
> }
>
> pid$target:Thread1::entry
> {
> put code here
> }
>
>
> This will be started with "script.d -c "Base args"
>
> This does not work because Thread1 has not yet been started. It will
> succeed if I make the first line of the script
>
> #!/usr/sbin/dtrace -Z -s
>
> but there will be no output from the code.
>
> On the other hand, if I just have the Base code, but do not have -Z,
> the statistics will appear, but only for Base.
>
> How do I see the Thread1 statistics
>
>
> --
> Sabba - סבא הלל - Hillel
> Hillel (Sabba) Markowitz | Said the fox to the fish, "Join me ashore"
> sabbahil...@gmail.com | The fish are the Jews, Torah is our water
> http://photos1.blogger.com/blogger/7637/544/640/SabbaHillel.jpg
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss@opensolaris.org
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
