From 8252ef0ad3457b5bd68fa16c40d7015a6728743c Mon Sep 17 00:00:00 2001 From: tenderlove Date: Sat, 30 May 2015 02:04:26 +0000 Subject: change lingering dtrace probe documentation from function- to method- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@50683 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- doc/dtrace_probes.rdoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc/dtrace_probes.rdoc') diff --git a/doc/dtrace_probes.rdoc b/doc/dtrace_probes.rdoc index a1e0fff3b0..d2cdd56902 100644 --- a/doc/dtrace_probes.rdoc +++ b/doc/dtrace_probes.rdoc @@ -9,10 +9,10 @@ specified. Probe definitions are in the format of: Since module and function cannot be specified, they will be blank. An example probe definition for Ruby would then be: - ruby:::function-entry(class name, method name, file name, line number) + ruby:::method-entry(class name, method name, file name, line number) Where "ruby" is the provider name, module and function names are blank, the -probe name is "function-entry", and the probe takes four arguments: +probe name is "method-entry", and the probe takes four arguments: * class name * method name @@ -59,15 +59,15 @@ with when they are fired and the arguments they take: [ruby:::method-return(classname, methodname, filename, lineno);] This probe is fired just after a method has returned. The arguments are the - same as "ruby:::function-entry". + same as "ruby:::method-entry". [ruby:::cmethod-entry(classname, methodname, filename, lineno);] This probe is fired just before a C method is entered. The arguments are the - same as "ruby:::function-entry". + same as "ruby:::method-entry". [ruby:::cmethod-return(classname, methodname, filename, lineno);] This probe is fired just before a C method returns. The arguments are the - same as "ruby:::function-entry". + same as "ruby:::method-entry". [ruby:::require-entry(requiredfile, filename, lineno);] This probe is fired on calls to rb_require_safe (when a file is required). -- cgit v1.2.3