Debugging Rails: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
This guide assumes that you are working from the command line to debug Ruby and Rails applications.
== Getting Started ==
== Getting Started ==
You can use rdebug for debugging Expertiza. The gem is already installed for you when you run <code>bundle install</code>.<br />
You can use rdebug for debugging Expertiza. The gem is already installed for you when you run <code>bundle install</code>.<br />
Line 7: Line 9:
<pre>
<pre>
(rdb:1) help
(rdb:1) help
ruby-debug help v0.10.4
Type 'help <command-name>' for help on a specific command
Available commands:
backtrace  delete  enable  help  method  putl    set    trace   
break      disable  eval    info  next    quit    show    undisplay
catch      display  exit    irb  p      reload  step    up     
condition  down    finish  kill  pp      restart  thread  var     
continue  edit    frame  list  ps      save    tmate  where
</pre>
</pre>
If you are familiar with gdb, the general commands are very similar.


== Sources ==
== Sources ==
* http://guides.rubyonrails.org/debugging_rails_applications.html
* http://guides.rubyonrails.org/debugging_rails_applications.html
* http://pivotallabs.com/ruby-debug-in-30-seconds-we-don-t-need-no-stinkin-gui
* http://pivotallabs.com/ruby-debug-in-30-seconds-we-don-t-need-no-stinkin-gui

Latest revision as of 16:08, 21 April 2013

This guide assumes that you are working from the command line to debug Ruby and Rails applications.

Getting Started

You can use rdebug for debugging Expertiza. The gem is already installed for you when you run bundle install.
To start debugging, you can run rdebug script/server from the Expertiza working directory.

Using Rdebug

You can ask rdebug for help by typing help in the rdb console.

(rdb:1) help
ruby-debug help v0.10.4
Type 'help <command-name>' for help on a specific command

Available commands:
backtrace  delete   enable  help  method  putl     set     trace    
break      disable  eval    info  next    quit     show    undisplay
catch      display  exit    irb   p       reload   step    up       
condition  down     finish  kill  pp      restart  thread  var      
continue   edit     frame   list  ps      save     tmate   where

If you are familiar with gdb, the general commands are very similar.

Sources