On Tue, Dec 8, 2009 at 3:25 PM, Angelo Rajadurai
<angelo.rajadu...@sun.com> wrote:
> 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:Base::entry
> /tid=3/
> {
> put code here
> }
>
> HTHs
>
> Angelo
Since I do not know the thread id, but the library or thread name is
known, how would I do it?
For example, the main executable is Base, it is built with various
libraries such as
gcc -g Base.c -o Base -l Thread1 -l Thread2 -l Thread3 (which are all
.so and used dynamically when the thread is needed).
When I set up the script as you showed it above, I do not get the
Threadn lists referring to probefunc that are called from within
Threadn.
A trivial hello world type test that does not use threads will allow
pid$target:hello::entry
{
code
}
pid$target:libc::entry
{
code
}
--
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
