Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 59a49ce

Browse files
committed
doc: Add blank line before bold text so it is rendered correctly
Signed-off-by: Eugene Loh <eugene.loh@oracle.com> Reviewed-by: Elena Zannoni <elena.zannoni@oracle.com>
1 parent 8e06271 commit 59a49ce

File tree

5 files changed

+5
-0
lines changed

5 files changed

+5
-0
lines changed

‎doc/userguide/reference/dtrace-ref-DTraceSupportforStrings.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,6 +132,7 @@ Returns 1 \(true\)
132132
Returns 0 \(false\)
133133

134134
</td></tr><tbody></table>
135+
135136
**Note:**
136137

137138
Identical Unicode strings might compare as being different if one or the other of the strings isn't normalized.

‎doc/userguide/reference/dtrace-ref-Variables.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -167,6 +167,7 @@ Yes
167167
Any probe that fires accesses an instance of the variable specific to that particular firing of the probe.
168168
169169
</td></tr><tbody></table>
170+
170171
**Note:**
171172
172173
Note the following information:

‎doc/userguide/reference/dtrace_providers_io.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,7 @@ Probe
139139
`fileinfo_t *`
140140

141141
</td></tr><tbody></table>
142+
142143
**Note:**
143144

144145
DTrace doesn't provide the option to use `fileinfo_t` with `io` probes. In Linux, no information is accessible at the level where the `io` probes fire about the file where an I/O request originated.

‎doc/userguide/reference/dtrace_providers_lockstat.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -241,6 +241,7 @@ Probe
241241
242242

243243
</td></tr><tbody></table>
244+
244245
**Note:**
245246

246247
`args[0]` has a pointer to the lock in question. The probes that fire in case of contention report a `uint64_t` `args[1]`, which is the wait time in nanoseconds. The `rw` probes also report an `int` that's either `RW_READER` or `RW_WRITER`. Finally, `adaptive-acquire-error` reports an `int` with a non zero error.

‎doc/userguide/reference/dtrace_providers_proc.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -124,6 +124,7 @@ Fires when a signal is sent to a process or to a thread created by a process. Th
124124
Fires in the context of a newly created process. The `start` probe fires before any user-level instructions are executed in the process.
125125

126126
</td></tr><tbody></table>
127+
127128
**Note:**
128129

129130
No fundamental difference between a process and a thread that a process creates, exists in Linux. The threads of a process are set up so that they can share resources, but each thread has its own entry in the process table with its own process ID.

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /