Skip to content

Commit

Permalink
Merge pull request #21320 from piton4eg/patch-8
Browse files Browse the repository at this point in the history
Small fixes [ci skip]
  • Loading branch information
senny committed Aug 24, 2015
2 parents 5abff7c + 0fb2600 commit a256a57
Showing 1 changed file with 8 additions and 7 deletions.
15 changes: 8 additions & 7 deletions guides/source/debugging_rails_applications.md
Expand Up @@ -351,6 +351,7 @@ by asking the debugger for help. Type: `help`
help -- prints this help.
help <cmd> -- prints help on command <cmd>.
help <cmd> <subcmd> -- prints help on <cmd>'s subcommand <subcmd>.
```

To see the previous ten lines you should type `list-` (or `l-`).

Expand Down Expand Up @@ -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
options:
* `thread` shows the current thread.
* `thread list` is used to list all threads and their statuses. The plus +
* `thread`: shows the current thread.
* `thread list`: is used to list all threads and their statuses. The plus +
character and the number indicates the current thread of execution.
* `thread stop _n_` stop thread _n_.
* `thread resume _n_` resumes thread _n_.
* `thread switch _n_` switches the current thread context to _n_.
* `thread stop _n_`: stop thread _n_.
* `thread resume _n_`: resumes thread _n_.
* `thread switch _n_`: switches the current thread context to _n_.
This command is very helpful when you are debugging concurrent threads and need
to verify that there are no race conditions in your code.
Expand Down Expand Up @@ -743,12 +744,12 @@ To list all active catchpoints use `catch`.
There are two ways to resume execution of an application that is stopped in the
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
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
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
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
Expand Down

0 comments on commit a256a57

Please sign in to comment.