aboutsummaryrefslogtreecommitdiffstats
path: root/railties/guides/source/debugging_rails_applications.textile
diff options
context:
space:
mode:
authorXavier Noria <fxn@hashref.com>2010-10-19 23:07:29 +0200
committerXavier Noria <fxn@hashref.com>2010-10-19 23:07:29 +0200
commitd619b9d1d1ad8d7497bf24283b2318c056283f48 (patch)
treed0a937b8630d4244eb91f45398dfe2be69ba6c45 /railties/guides/source/debugging_rails_applications.textile
parent95d87823d4c9837e7a491fb4469869c5b2de5e05 (diff)
parente43de58ab449218ab2d56e30e54e429aadcb8a1b (diff)
downloadrails-d619b9d1d1ad8d7497bf24283b2318c056283f48.tar.gz
rails-d619b9d1d1ad8d7497bf24283b2318c056283f48.tar.bz2
rails-d619b9d1d1ad8d7497bf24283b2318c056283f48.zip
Merge branch 'master' of git://github.com/lifo/docrails
Diffstat (limited to 'railties/guides/source/debugging_rails_applications.textile')
-rw-r--r--railties/guides/source/debugging_rails_applications.textile4
1 files changed, 1 insertions, 3 deletions
diff --git a/railties/guides/source/debugging_rails_applications.textile b/railties/guides/source/debugging_rails_applications.textile
index 35069f33ad..b9d45fb13a 100644
--- a/railties/guides/source/debugging_rails_applications.textile
+++ b/railties/guides/source/debugging_rails_applications.textile
@@ -250,7 +250,7 @@ Make sure you have started your web server with the option +--debugger+:
<shell>
~/PathTo/rails_project$ rails server --debugger
-=> Booting Mongrel (use 'rails server webrick' to force WEBrick)
+=> Booting WEBrick
=> Rails 3.0.0 application starting on http://0.0.0.0:3000
=> Debugger enabled
...
@@ -258,8 +258,6 @@ Make sure you have started your web server with the option +--debugger+:
TIP: In development mode, you can dynamically +require \'ruby-debug\'+ instead of restarting the server, if it was started without +--debugger+.
-In order to use Rails debugging you'll need to be running either *WEBrick* or *Mongrel*. For the moment, no alternative servers are supported.
-
h4. The Shell
As soon as your application calls the +debugger+ method, the debugger will be started in a debugger shell inside the terminal window where you launched your application server, and you will be placed at ruby-debug's prompt +(rdb:n)+. The _n_ is the thread number. The prompt will also show you the next line of code that is waiting to run.