A list of DTrace probes and their functionality. “Module” and “Function” cannot be defined in user defined probes (known as USDT), so they will not be specified. Probe definitions are in the format of:
provider:module:function:name(arguments)
Since module and function cannot be specified, they will be blank. An example probe definition for Ruby would then be:
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 “method-entry”, and the probe takes four arguments:
class name
method name
file name
line number
Before we list the specific probes, let’s talk about stability. Probe stability is declared in the probes.d file at the bottom on the pragma D attributes lines. Here is a description of each of the stability declarations.
The provider name of “ruby” has been declared as stable. It is unlikely that we will change the provider name from “ruby” to something else.
Since we are not allowed to provide values for the module and function name, the values we have provided (no value) is declared as stable.
The probe names are likely to change in the future, so they are marked as “Evolving”. Consumers should not depend on these names to be stable.
The parameters passed to the probes are likely to change in the future, so they are marked as “Evolving”. Consumers should not depend on these to be stable.
Probes are defined in the probes.d file. Here are the declared probes along with when they are fired and the arguments they take:
This probe is fired just before a method is entered.
name of the class (a string)
name of the method about to be executed (a string)
the file name where the method is _being called_ (a string)
the line number where the method is _being called_ (an int)
NOTE: will only be fired if tracing is enabled, e.g. with:
TracePoint.new{}.enable
. See Feature#14104 for more
details.
This probe is fired just after a method has returned. The arguments are the same as “ruby:::method-entry”.
NOTE: will only be fired if tracing is enabled, e.g. with:
TracePoint.new{}.enable
. See Feature#14104 for more
details.
This probe is fired just before a C method is entered. The arguments are the same as “ruby:::method-entry”.
This probe is fired just before a C method returns. The arguments are the same as “ruby:::method-entry”.
This probe is fired on calls to rb_require_safe (when a file is required).
the name of the file to be required (string).
the file that called “require
” (string).
the line number where the call to require was made (int).
This probe is fired just before rb_require_safe (when a file is required) returns. The arguments are the same as “ruby:::require-entry”. This probe will not fire if there was an exception during file require.
This probe is fired right before search_required is called. search_required
determines whether the file has already been required by searching loaded
features ($"
), and if not, figures out which file must be
loaded.
the file to be required (string).
the file that called “require” (string).
the line number where the call to require was made (int).
This probe is fired right after search_required returns. See the documentation for “ruby:::find-require-entry” for more details. Arguments for this probe are the same as “ruby:::find-require-entry”.
This probe is fired when calls to “load” are made. The arguments are the same as “ruby:::require-entry”.
This probe is fired when “load” returns. The arguments are the same as “ruby:::load-entry”.
This probe is fired when an exception is raised.
the class name of the raised exception (string)
the name of the file where the exception was raised (string)
the line number in the file where the exception was raised (int)
This probe is fired when an object is about to be allocated.
the class of the allocated object (string)
the name of the file where the object is allocated (string)
the line number in the file where the object is allocated (int)
This probe is fired when an Array is about to be allocated.
the size of the array (long)
the name of the file where the array is allocated (string)
the line number in the file where the array is allocated (int)
This probe is fired when a Hash is about to be allocated.
the size of the hash (long)
the name of the file where the hash is allocated (string)
the line number in the file where the hash is allocated (int)
This probe is fired when a String is about to be allocated.
the size of the string (long)
the name of the file where the string is allocated (string)
the line number in the file where the string is allocated (int)
This probe is fired when a Symbol is about to be allocated.
the contents of the symbol (string)
the name of the file where the string is allocated (string)
the line number in the file where the string is allocated (int)
Fired just before parsing and compiling a source file.
the file being parsed (string)
the line number where the source starts (int)
Fired just after parsing and compiling a source file.
the file being parsed (string)
the line number where the source ended (int)
Fired at the beginning of a mark phase.
Fired at the end of a mark phase.
Fired at the beginning of a sweep phase.
Fired at the end of a sweep phase.
Fired when the method cache is cleared.
the classname being cleared, or “global” (string)
the file being parsed (string)
the line number where the source ended (int)