I'll try that. Thank you very much for your info !
Jianhua Yang -----Original Message----- From: perf-discuss-boun...@opensolaris.org [mailto:perf-discuss-boun...@opensolaris.org] On Behalf Of johan...@opensolaris.org Sent: Tuesday, May 04, 2010 8:08 PM To: Jianhua Yang Cc: perf-discuss@opensolaris.org Subject: Re: [perf-discuss] pid$target: Not enough space On Tue, May 04, 2010 at 03:23:09PM -0700, Jianhua Yang wrote: > I wanted to find out what the single threaded process was doing with dtrace > but it returned with "Not enough space"error: > > # dtrace -ln 'pid$target:::entry,pid$target:::return {trace(timestamp);}' -p > 25050 > dtrace: invalid probe specifier pid$target:::entry,pid$target:::return > {trace(timestamp);}: failed to create return probe for 'kdstf1011000km': Not > enough space > > questions are: > what does "Not enough space" means ? > how to avoid such errors ? There's a limit to the number of pid probes that can be created at a single time. For my shell, this seems to work: dtrace -l -n "pid$$:::entry" -p $$ However, 'dtrace -l -Ppid$$ -p $$" generates a no-space error. Often times, if you can narrow down the probe specification you'll reduce the number of functions to the point where you won't exceed the limit. It's also possible to increase the limit of available pid probes, but it's still possible to hit the ENOSPC error. You don't want DTrace to use up all of your memory. http://www.solarisinternals.com/wiki/index.php/DTrace_Topics_Errors#failed_to_create_probe_..._Not_enough_space -j _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org --- This communication may contain confidential and/or privileged information. If you are not the intended recipient (or have received this communication in error) please notify the sender immediately and destroy this communication. Any unauthorized copying, disclosure or distribution of the material in this communication is strictly forbidden. Deutsche Bank does not render legal or tax advice, and the information contained in this communication should not be regarded as such. _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
