mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
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
This commit is contained in:
parent
354c9747e4
commit
8252ef0ad3
3 changed files with 13 additions and 8 deletions
|
@ -1,3 +1,8 @@
|
|||
Sat May 30 11:02:55 2015 Martin Englund <martin@englund.nu>
|
||||
|
||||
* doc/dtrace_probes.rdoc: change lingering dtrace probe documentation
|
||||
from function- to method-
|
||||
|
||||
Sat May 30 10:26:09 2015 Masaki Matsushita <glass.saga@gmail.com>
|
||||
|
||||
* lib/tempfile.rb: refactoring.
|
||||
|
|
|
@ -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).
|
||||
|
|
6
probes.d
6
probes.d
|
@ -17,7 +17,7 @@ provider ruby {
|
|||
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 {
|
|||
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);
|
||||
|
||||
|
|
Loading…
Reference in a new issue