I've been having similar issues. There is apparently a fork of the project called simply 'debugger' as the original ruby-debug seems to have been abandoned (heresay).
Let me know if you find a solution; debugger didn't work for me, but it is likely that my system is borked uniquely as most I know have no trouble.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/sqg6Oyhtz7wJ.
To post to this group, send email to rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
> I'm trying to get the ruby debugger working and can't seem to get there. Environment summary:
>
> Mac OS X Lion
> RVM
> Ruby 1.9.3p125
> Rails 3.2.3
> Rspec 2.9.0
>
> I've put the debugger statement in my controller like so:
>
> def show
> debugger
> seasons = Season.where(:name=>params[:id])
> puts @seasons
> @season = seasons.first
> puts @season
> @season_entries = @season.season_entries
> end
>
> And run my spec like so:
>
> $ bundle exec rspec -d spec/controllers/seasons_controller_spec.rb
try $ RUBYOPT='-r openssl' bundle exec rspec -d spec/controllers/seasons_controller_spec.rb
it looks weird but usually works :)
--
===============================================================================
Tomas Meinlschmidt, MS {MCT, MCP+I, MCSE, AER}, NetApp Filer/NetCache
www.meinlschmidt.com www.maxwellrender.cz www.lightgems.cz
===============================================================================
try $ RUBYOPT='-r openssl' bundle exec rspec -d spec/controllers/seasons_controller_spec.rb
it looks weird but usually works :)
I've been having similar issues. There is apparently a fork of the project called simply 'debugger' as the original ruby-debug seems to have been abandoned (heresay).
Let me know if you find a solution; debugger didn't work for me, but it is likely that my system is borked uniquely as most I know have no trouble.
-David
Perfect, thanks! If only Ryan had posted this a couple days earlier, would have saved me a few hours :)
-David
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/j9U5tLmWfwEJ.