Fix option display for operf
when a line starts with a [term] like [option] AsciiDoc reads this as a role for the next block. By adding a dummy hard return, `+` to the end of the line we override this behavior
This commit is contained in:
parent
59921db098
commit
b9a7011691
1 changed files with 2 additions and 2 deletions
|
|
@ -73,9 +73,9 @@ Before OProfile can be run in legacy mode, it must be configured as shown in xre
|
|||
|
||||
Replace _options_ with the desired command-line options to specify your profiling settings. Full set of options is described in `operf(1)` manual page. Replace _range_ with one of the following:
|
||||
|
||||
[option]`--system-wide` - this setting allows for global profiling, see xref:OProfile.adoc#using_operf_system-wide[Using [command]#operf# in System-wide Mode]
|
||||
[option]`--system-wide` - this setting allows for global profiling, see xref:OProfile.adoc#using_operf_system-wide[Using [command]#operf# in System-wide Mode] +
|
||||
|
||||
[option]`--pid=pass:attributes[{blank}]_PID_pass:attributes[{blank}]` - this is to profile a running application, where _PID_ is the process ID of the process you want to profile.
|
||||
[option]`--pid=pass:attributes[{blank}]_PID_pass:attributes[{blank}]` - this is to profile a running application, where _PID_ is the process ID of the process you want to profile. +
|
||||
|
||||
With _command_ and _args_, you can define a specific command or application to be profiled, and also the input arguments that this command or application requires. Either _command_, [option]`--pid` or [option]`--system-wide` is required, but these cannot be used simultaneously.
|
||||
|
||||
|
|
|
|||
Reference in a new issue