diff options
| author | Ryan Petrello <rpetrell@redhat.com> | 2018-02-27 00:27:35 +0100 |
|---|---|---|
| committer | Ryan Petrello <rpetrell@redhat.com> | 2018-02-27 01:05:50 +0100 |
| commit | d743b773532ceeb732ee283b348fff770123b5cd (patch) | |
| tree | 390d70fa7a959faa5c78d19ff3cbebbc67615d26 /docs | |
| parent | Merge pull request #1357 from mabashian/1281-prompt-inv (diff) | |
| download | awx-d743b773532ceeb732ee283b348fff770123b5cd.tar.xz awx-d743b773532ceeb732ee283b348fff770123b5cd.zip | |
replace our rdb tooling w/ the sdb PyPI package
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/debugging.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/debugging.md b/docs/debugging.md index ee0405af3b..1257a8cf11 100644 --- a/docs/debugging.md +++ b/docs/debugging.md @@ -9,7 +9,7 @@ Python processes in Tower's development environment are kept running in the background via supervisord. As such, interacting with them via Python's standard `pdb.set_trace()` isn't possible. -Bundled in our container environment is a remote debugging tool, `rdb`. You +Bundled in our container environment is a remote debugging tool, `sdb`. You can use it to set remote breakpoints in Tower code and debug interactively over a telnet session: @@ -28,8 +28,8 @@ a telnet session: # You can access it from your host machine using telnet: # # $ telnet localhost <port> - import rdb - rdb.set_trace() + import sdb + sdb.set_trace() ``` Keep in mind that when you interactively debug in this way, any process @@ -43,8 +43,8 @@ remote debugging sessions and automatically connect to them. From your *host* machine (i.e., _outside_ of the development container), you can run: ``` -make rdb +sdb-listen ``` This will open a Python process that listens for new debugger sessions and -automatically connects to them for you.
\ No newline at end of file +automatically connects to them for you. |