diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-02-18 13:34:06 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-02-18 13:34:06 +0300 |
| commit | 859a6fb938bb9ee2a317c46dfa4fcc1af49608f0 (patch) | |
| tree | d7f2700abe6b4ffcb2dcfc80631b2d87d0609239 /doc/development/pry_debugging.md | |
| parent | 446d496a6d000c73a304be52587cd9bbc7493136 (diff) | |
Add latest changes from gitlab-org/gitlab@13-9-stable-eev13.9.0-rc42
Diffstat (limited to 'doc/development/pry_debugging.md')
| -rw-r--r-- | doc/development/pry_debugging.md | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/development/pry_debugging.md b/doc/development/pry_debugging.md index f29e0d403cd..d662e6bbc54 100644 --- a/doc/development/pry_debugging.md +++ b/doc/development/pry_debugging.md @@ -10,7 +10,10 @@ info: To determine the technical writer assigned to the Stage/Group associated w To invoke the debugger, place `binding.pry` somewhere in your code. When the Ruby interpreter hits that code, execution stops, -and you can type in commands to debug the state of the program +and you can type in commands to debug the state of the program. + +When debugging code in another process like Puma or Sidekiq, you can use `binding.remote_pry`. +You can then connect to this session by running `pry-remote` from your terminal. ## `byebug` vs `binding.pry` @@ -79,7 +82,7 @@ Similar to source browsing, is [Documentation browsing](https://github.com/pry/p ### Command history -With **Ctrl+R** you can search your [command history](https://github.com/pry/pry/wiki/History). +With <kbd>Control</kbd> + <kbd>R</kbd> you can search your [command history](https://github.com/pry/pry/wiki/History). ## Stepping |