Hi Thomas, Can you send the invocations of dtrace(1M) that you're using? What do you see if you do this: dtrace -l -n pid<yourpid>:::entry
Adam On Mon, Aug 25, 2008 at 07:58:50AM -0700, Thomas Mohme wrote: > I'm trying to do some userspace tracing on a server-process with the pid > provider. > My problem is, that the only probes the pid-provider lists for the > server-process (to which I attach dtrace with "-p nnnn") are coming from > "ld.so.1". > There's not a single one from my modules. > If I'm specifying "a.out" (or any of our shared-objects) as the module, I > only get "No probe matches description". > Tracing with the syscall-provider shows no problem, but is way too > fine-grained for my purpose. > When I'm attaching mdb to the server-process, "::objects" and "::nm" show me > lots of our stuff. > > The server-process runs in a non-global zone, I'm trying to run dtrace in the > global zone. > The mdb-commands ran in the same zone as the server-process. > > With our Solaris 10 (11/06) local-zone dtrace should work, but I only get > "DTrace device not available in local zone" as response :( > > Any idea what I'm doing wrong? > Is there a restriction regarding cross-zone tracing with the pid-provider? > > Thomas > > > -- > This message posted from opensolaris.org > _______________________________________________ > dtrace-discuss mailing list > [email protected] -- Adam Leventhal, Fishworks http://blogs.sun.com/ahl _______________________________________________ dtrace-discuss mailing list [email protected]
