Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
e8c974c8
Commit
e8c974c8
authored
May 19, 2021
by
Mehmet Emin INAC
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update the `pry debugging` docs
parent
aad69af5
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
2 deletions
+4
-2
doc/development/pry_debugging.md
doc/development/pry_debugging.md
+4
-2
No files found.
doc/development/pry_debugging.md
View file @
e8c974c8
...
...
@@ -12,8 +12,10 @@ 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.
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.
When debugging code in another process like Puma or Sidekiq, you can use
`binding.pry_shell`
.
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`
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment