Hey Eric, There's not a great way to do it, but you can use a tool like mdb(1) on Solaris, or a simple DTrace script:
---8<--- dtrace_probes.d ---8<--- #!/usr/sbin/dtrace -s #pragma D option quiet int i; tick-100 /i >= `dtrace_nprobes/ { exit(0); } tick-100 { printf("%4d %10s %20s %20s %10s %s\n", i, stringof(`dtrace_probes[i]->dtpr_provider->dtpv_name), stringof(`dtrace_probes[i]->dtpr_mod), stringof(`dtrace_probes[i]->dtpr_func), stringof(`dtrace_probes[i]->dtpr_name), `dtrace_probes[i]->dtpr_ecb != NULL ? "enabled" : "disabled"); i++ } ---8<--- dtrace_probes.d ---8<--- 0 dtrace BEGIN disabled 1 dtrace END disabled 2 dtrace ERROR enabled 3 python589 libpython2.6.so.1.0 PyEval_EvalFrameEx function-entry disabled 4 python589 libpython2.6.so.1.0 dtrace_entry function-entry disabled Unfortunately this doesn't work on Mac OS X: # dtrace -n 'BEGIN{ trace(`dtrace_nprobes); }' dtrace: invalid probe specifier BEGIN{ trace(`dtrace_nprobes); }: in action list: failed to resolve `dtrace_nprobes: Unknown symbol name Some kernel symbols seem to be available; perhaps someone more familiar with Mac OS X can get this script running over there. Adam On Tue, Jun 21, 2011 at 5:01 AM, Eric Gorr <mail...@ericgorr.net> wrote: > If it matters, I am using Mac OS X 10.6.x. > > Let's say that I open a terminal window, enabled a few probes, and start > collecting data. > > From a different terminal window can I ask DTrace what probes have been > enabled? If so, how? > > Thank you. > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss@opensolaris.org > -- Adam Leventhal, Delphix http://dtrace.org/blogs/ahl 275 Middlefield Road, Suite 50 Menlo Park, CA 94025 http://www.delphix.com _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org