Commit 4b625a91 authored by charlie ablett's avatar charlie ablett

Merge branch 'update_pry_debugging_docs' into 'master'

Update pry debugging docs

See merge request gitlab-org/gitlab!62122
parents 1121c640 4271419a
...@@ -930,7 +930,7 @@ GEM ...@@ -930,7 +930,7 @@ GEM
pry (~> 0.13.0) pry (~> 0.13.0)
pry-rails (0.3.9) pry-rails (0.3.9)
pry (>= 0.10.4) pry (>= 0.10.4)
pry-shell (0.4.0) pry-shell (0.4.1)
pry (~> 0.13.0) pry (~> 0.13.0)
tty-markdown tty-markdown
tty-prompt tty-prompt
......
---
title: Fix `pry` debugging location with `pry-byebug` and `pry-shell` by updating the `pry-shell` gem
merge_request: 62122
author:
type: fixed
...@@ -12,8 +12,10 @@ To invoke the debugger, place `binding.pry` somewhere in your ...@@ -12,8 +12,10 @@ To invoke the debugger, place `binding.pry` somewhere in your
code. When the Ruby interpreter hits that code, execution stops, 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`. When debugging code in another process like Puma or Sidekiq, you can use `binding.pry_shell`.
You can then connect to this session by running `pry-remote` from your terminal. You can then connect to this session by using the [pry-shell](https://github.com/meinac/pry-shell) executable.
You can watch [this video](https://www.youtube.com/watch?v=Lzs_PL_BySo), for more information about
how to use the `pry-shell`.
## `byebug` vs `binding.pry` ## `byebug` vs `binding.pry`
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment