mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
Fix docs for debugging [ci skip]:
* fix command list for thread * add omitted end of code * fix description for `continue` and `finish` command
This commit is contained in:
parent
95cb2e3a8a
commit
0fb2600bbb
1 changed files with 8 additions and 7 deletions
|
@ -351,6 +351,7 @@ by asking the debugger for help. Type: `help`
|
||||||
help -- prints this help.
|
help -- prints this help.
|
||||||
help <cmd> -- prints help on command <cmd>.
|
help <cmd> -- prints help on command <cmd>.
|
||||||
help <cmd> <subcmd> -- prints help on <cmd>'s subcommand <subcmd>.
|
help <cmd> <subcmd> -- prints help on <cmd>'s subcommand <subcmd>.
|
||||||
|
```
|
||||||
|
|
||||||
To see the previous ten lines you should type `list-` (or `l-`).
|
To see the previous ten lines you should type `list-` (or `l-`).
|
||||||
|
|
||||||
|
@ -458,12 +459,12 @@ The debugger can list, stop, resume and switch between running threads by using
|
||||||
the `thread` command (or the abbreviated `th`). This command has a handful of
|
the `thread` command (or the abbreviated `th`). This command has a handful of
|
||||||
options:
|
options:
|
||||||
|
|
||||||
* `thread` shows the current thread.
|
* `thread`: shows the current thread.
|
||||||
* `thread list` is used to list all threads and their statuses. The plus +
|
* `thread list`: is used to list all threads and their statuses. The plus +
|
||||||
character and the number indicates the current thread of execution.
|
character and the number indicates the current thread of execution.
|
||||||
* `thread stop _n_` stop thread _n_.
|
* `thread stop _n_`: stop thread _n_.
|
||||||
* `thread resume _n_` resumes thread _n_.
|
* `thread resume _n_`: resumes thread _n_.
|
||||||
* `thread switch _n_` switches the current thread context to _n_.
|
* `thread switch _n_`: switches the current thread context to _n_.
|
||||||
|
|
||||||
This command is very helpful when you are debugging concurrent threads and need
|
This command is very helpful when you are debugging concurrent threads and need
|
||||||
to verify that there are no race conditions in your code.
|
to verify that there are no race conditions in your code.
|
||||||
|
@ -741,12 +742,12 @@ To list all active catchpoints use `catch`.
|
||||||
There are two ways to resume execution of an application that is stopped in the
|
There are two ways to resume execution of an application that is stopped in the
|
||||||
debugger:
|
debugger:
|
||||||
|
|
||||||
* `continue` [line-specification] \(or `c`): resume program execution, at the
|
* `continue [line-specification]` \(or `c`): resume program execution, at the
|
||||||
address where your script last stopped; any breakpoints set at that address are
|
address where your script last stopped; any breakpoints set at that address are
|
||||||
bypassed. The optional argument line-specification allows you to specify a line
|
bypassed. The optional argument line-specification allows you to specify a line
|
||||||
number to set a one-time breakpoint which is deleted when that breakpoint is
|
number to set a one-time breakpoint which is deleted when that breakpoint is
|
||||||
reached.
|
reached.
|
||||||
* `finish` [frame-number] \(or `fin`): execute until the selected stack frame
|
* `finish [frame-number]` \(or `fin`): execute until the selected stack frame
|
||||||
returns. If no frame number is given, the application will run until the
|
returns. If no frame number is given, the application will run until the
|
||||||
currently selected frame returns. The currently selected frame starts out the
|
currently selected frame returns. The currently selected frame starts out the
|
||||||
most-recent frame or 0 if no frame positioning (e.g up, down or frame) has been
|
most-recent frame or 0 if no frame positioning (e.g up, down or frame) has been
|
||||||
|
|
Loading…
Reference in a new issue