diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-11-26 06:09:17 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-11-26 06:09:17 +0300 |
commit | 846ebeb02e405ed42f8a45f34e941c70e3ca2ee3 (patch) | |
tree | 279a4c230e190a08428a1a575c09ef15113cb844 /doc/development/pry_debugging.md | |
parent | 9331523ddc35cee6d42f73f31b1567478a4298c4 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/pry_debugging.md')
-rw-r--r-- | doc/development/pry_debugging.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/pry_debugging.md b/doc/development/pry_debugging.md index 7f9a49d4d50..eac84a3f13d 100644 --- a/doc/development/pry_debugging.md +++ b/doc/development/pry_debugging.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w ## Invoking pry debugging To invoke the debugger, place `binding.pry` somewhere in your -code. When the Ruby interpreter hits that code, execution will stop, +code. When the Ruby interpreter hits that code, execution stops, and you can type in commands to debug the state of the program ## `byebug` vs `binding.pry` @@ -20,7 +20,7 @@ use the powerful Pry REPL. `binding.pry` uses Pry, but lacks some of the `byebug` features. GitLab uses the [`pry-byebug`](https://github.com/deivid-rodriguez/pry-byebug) gem. This gem brings some capabilities `byebug` to `binding.pry`, so -using that, will give you the most debugging powers. +using that gives you the most debugging powers. ## `byebug` @@ -104,7 +104,7 @@ You also can move around in the callstack with these commands: - `down`: Moves the stack frame down. Takes an optional numeric argument to move multiple frames. - `frame <n>`: Moves to a specific frame. Called without arguments - will show the current frame. + displays the current frame. ## Short commands |