ruby-changes:38602
From: tenderlove <ko1@a...>
Date: Sat, 30 May 2015 11:05:01 +0900 (JST)
Subject: [ruby-changes:38602] tenderlove:r50683 (trunk): change lingering dtrace probe documentation from function- to method-
tenderlove 2015-05-30 11:04:26 +0900 (Sat, 30 May 2015) New Revision: 50683 http://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=revision&revision=50683 Log: change lingering dtrace probe documentation from function- to method- Modified files: trunk/ChangeLog trunk/doc/dtrace_probes.rdoc trunk/probes.d Index: doc/dtrace_probes.rdoc =================================================================== --- doc/dtrace_probes.rdoc (revision 50682) +++ doc/dtrace_probes.rdoc (revision 50683) @@ -9,10 +9,10 @@ specified. Probe definitions are in the https://github.com/ruby/ruby/blob/trunk/doc/dtrace_probes.rdoc#L9 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 argumen https://github.com/ruby/ruby/blob/trunk/doc/dtrace_probes.rdoc#L59 [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). Index: ChangeLog =================================================================== --- ChangeLog (revision 50682) +++ ChangeLog (revision 50683) @@ -1,3 +1,8 @@ https://github.com/ruby/ruby/blob/trunk/ChangeLog#L1 +Sat May 30 11:02:55 2015 Martin Englund <martin@e...> + + * doc/dtrace_probes.rdoc: change lingering dtrace probe documentation + from function- to method- + Sat May 30 10:26:09 2015 Masaki Matsushita <glass.saga@g...> * lib/tempfile.rb: refactoring. Index: probes.d =================================================================== --- probes.d (revision 50682) +++ probes.d (revision 50683) @@ -17,7 +17,7 @@ provider ruby { https://github.com/ruby/ruby/blob/trunk/probes.d#L17 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". + the same as "ruby:::method-entry". */ probe method__return(const char *classname, const char *methodname, const char *filename, int lineno); @@ -25,14 +25,14 @@ provider ruby { https://github.com/ruby/ruby/blob/trunk/probes.d#L25 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". + the same as "ruby:::method-entry". */ probe cmethod__entry(const char *classname, const char *methodname, const char *filename, int lineno); /* 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". + the same as "ruby:::method-entry". */ probe cmethod__return(const char *classname, const char *methodname, const char *filename, int lineno); -- ML: ruby-changes@q... Info: http://www.atdot.net/~ko1/quickml/