From 6f80ea2aec83523640b505ddd5b6e87f0100a85b Mon Sep 17 00:00:00 2001 From: Aditya Sanghi Date: Wed, 18 Apr 2012 00:48:59 +0530 Subject: [PATCH] review changes for #5875 --- .../lib/active_support/core_ext/kernel/debugger.rb | 2 +- guides/code/getting_started/README.rdoc | 2 +- guides/source/debugging_rails_applications.textile | 8 ++++---- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/activesupport/lib/active_support/core_ext/kernel/debugger.rb b/activesupport/lib/active_support/core_ext/kernel/debugger.rb index a2347111b5..0d9456641a 100644 --- a/activesupport/lib/active_support/core_ext/kernel/debugger.rb +++ b/activesupport/lib/active_support/core_ext/kernel/debugger.rb @@ -1,6 +1,6 @@ module Kernel unless respond_to?(:debugger) - # Starts a debugging session if debugger has been loaded (call rails server --debugger to do load it). + # Starts a debugging session if +debugger+ gem has been loaded (call rails server --debugger to do load it). def debugger message = "\n***** Debugger requested, but was not available (ensure debugger is listed in Gemfile/installed as gem): Start server with --debugger to enable *****\n" defined?(Rails) ? Rails.logger.info(message) : $stderr.puts(message) diff --git a/guides/code/getting_started/README.rdoc b/guides/code/getting_started/README.rdoc index 465c180c44..06cc2635b7 100644 --- a/guides/code/getting_started/README.rdoc +++ b/guides/code/getting_started/README.rdoc @@ -87,7 +87,7 @@ Debugger support is available through the debugger command when you start your Mongrel or WEBrick server with --debugger. This means that you can break out of execution at any point in the code, investigate and change the model, and then, resume execution! You need to install debugger to run the server in debugging -mode. With gems, use sudo gem install debugger. Example: +mode. With gems, use gem install debugger. Example: class WeblogController < ActionController::Base def index diff --git a/guides/source/debugging_rails_applications.textile b/guides/source/debugging_rails_applications.textile index 8b6e914291..ed91999496 100644 --- a/guides/source/debugging_rails_applications.textile +++ b/guides/source/debugging_rails_applications.textile @@ -202,16 +202,16 @@ h4. Setup The debugger used by Rails, +debugger+, comes as a gem. To install it, just run: -$ sudo gem install debugger +$ gem install debugger -TIP: If you are using Ruby 1.9, you can install a compatible version of +ruby-debug+ by running +sudo gem install debugger+ +TIP: If you are using Ruby 1.9, you can install a compatible version of +ruby-debug+ by running +gem install debugger+ In case you want to download a particular version or get the source code, refer to the "project's page on rubyforge":http://rubyforge.org/projects/ruby-debug/. Rails has had built-in support for ruby-debug since Rails 2.0. Inside any Rails application you can invoke the debugger by calling the +debugger+ method. -ruby-debug19 has had a number of compatibility issues with ruby 1.9.3+ and as such the ball has been picked to maintain the ruby debugging gem in the newer "debugger" gem. ++ruby-debug19+ gem has been replaced by the +debugger+ gem due to multiple issues on Ruby 1.9.3. Here's an example: @@ -639,7 +639,7 @@ If a Ruby object does not go out of scope, the Ruby Garbage Collector won't swee To install it run: -$ sudo gem install bleak_house +$ gem install bleak_house Then setup your application for profiling. Then add the following at the bottom of config/environment.rb: