Hey Ravi:
You are trying to create a probe for every function in the oracle
binary. Is this what you want to do? By default you can have up to
250000 probes in the system. Looks like you are running out of probes.
You can increase the probes by changing the fasttrap-max-probes
variable in the /kernel/drv/fasttrap.conf file. Once you increase the
value then run "update_drv fasttrap" or reboot.
If you are trying to find out the most expensive function in the
Oracle process then a easier and less intrusive way is to use the
profile probe. Here is a simple script that will give you relative
numbers rather than absolute numbers. The profile probe wakes up at
regular intervals and see what is running at that time and records the
details.
dtrace -n profile-1001'/pid==17977/{...@[ufunc(arg1)]=count()}'
You can modify the predicate to fit your need. The ufunc() action
takes an address and provides name of function. arg1 is set to the PC
if the current process is executing in the user land.
HTHs
Angelo
On Oct 27, 2009, at 8:54 PM, Ravi Swaminathan wrote:
Hi,
I am looking for information on what could be causing this message.
dtrace: invalid probe specifier pid17977:oracle::entry { @[probename]
=count(); } : failed to create entry probe for 'pmucmex': Not enough
space
--
Thanks and Regards,
Ravi Swaminathan
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
