Skip to content

Commit

Permalink
[DOC] Fixed markups in dtrace_probes.rdoc [ci skip]
Browse files Browse the repository at this point in the history
* `+` can enclose just a word.
* TIDYLINK with braces gets confused when other braces even inside
  code precede.
  • Loading branch information
nobu committed Dec 19, 2020
1 parent 144b11e commit a5832c9
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions doc/dtrace_probes.rdoc
Expand Up @@ -56,16 +56,16 @@ with when they are fired and the arguments they take:
methodname name of the method about to be executed (a string)
filename the file name where the method is _being called_ (a string)
lineno 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 {ticket #14104}[https://bugs.ruby-lang.org/issues/14104] for more details.

*NOTE*: will only be fired if tracing is enabled, e.g. with: <code>TracePoint.new{}.enable</code>.
See Feature#14104[https://bugs.ruby-lang.org/issues/14104] for more details.

[ruby:::method-return(classname, methodname, filename, lineno);]
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 {ticket #14104}[https://bugs.ruby-lang.org/issues/14104] for more details.

*NOTE*: will only be fired if tracing is enabled, e.g. with: <code>TracePoint.new{}.enable</code>.
See Feature#14104[https://bugs.ruby-lang.org/issues/14104] for more details.

[ruby:::cmethod-entry(classname, methodname, filename, lineno);]
This probe is fired just before a C method is entered. The arguments are the
Expand Down

0 comments on commit a5832c9

Please sign in to comment.