Hi Hillel:
Just want to clarify the terminologies here. What you have here is dynamic
libraries and not threads.
Try
pid$target:*Thread1*::entry
{
put your code here
}
See if this works. You do not need to use the -Z.
-Angelo
On Dec 8, 2009, at 3:58 PM, Hillel (Sabba) Markowitz
On Wed, Dec 9, 2009 at 9:15 AM, Angelo Rajadurai
angelo.rajadu...@sun.com wrote:
Hi Hillel:
Just want to clarify the terminologies here. What you have here is dynamic
libraries and not threads.
Try
pid$target:*Thread1*::entry
{
put your code here
}
See if this works. You do
Thanks. I got confused between threads and dynamic modules. It
actually turns out that if I put the -Z' in the script as
#!/usr/sbin/dtrace -Z -s
There is no output. On the other hand, if I set it up as
#!/usr/sbin/dtrace -s
Remember that shell scripts can provide at most one option
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
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
