ruby-debug

I can't get my ruby-debug-ide to work properly. I have a basic rails app, and I would like to debug in RubyMine. Before I even start RubyMine, I need to enable rdebug-ide in my vagrant VM. When I navigate to my project directory, I have read online I need to enter the following command: rdebug-ide --port 1236 --dispatcher-port 26166 --host 0.0.0.0 - bin/rails s -b 0.0.0.0 However when I run this command, I get this message: I have also tried a modified version of the above command: (an extra dash) rdebug-ide --port 1236 --dispatcher-port 26166 --host 0.0.0.0 -- bin/rails s -b 0.0.0.0 And I get

Say I have a loop in my code that calls the rails debugger a few times def show animals = ['dog', 'cat', 'owl', 'tiger'] for animal in animals debugger # do something else end Assuming I started my server with the --debugger option, when this page is viewed, the debugger is going to stop for every run of the loop. I can type cont every time it stops so the request continues, but that's tedious, especially if we're not talking about it showing up 4 times as in this example, but 400. Is there a way to let the debugger continue without pausing at each point of the loop? My currently workaround is

I'm try to add a debugger to my rails 3.1.1 application which uses ruby 1.9.2. I have added the following to my gemfile: gem 'ruby-debug19', :require => 'ruby-debug' and I get the following error: /.rvm/gems/ruby-1.9.2-p290@rails31/gems/ruby-debug19-0.11.6/cli/ruby-debug/interface.rb:55:in `block (2 levels) in initialize': uninitialized constant Debugger::LocalInterface::Readline (NameError) by the way i have the following: $ ruby -v ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-linux] $ rails -v Rails 3.1.1 $ rvm -v rvm 1.8.6 by Wayne E. Seguin (wayneeseguin@gmail.com) [https://rvm

I'm trying to debug simple ruby file in Aptana 3. class HelloWorld def initialize() end def greet() puts "hello world" end end h=HelloWorld.new h.greet breakpoint is set to h.greet after I started debug, debugger starts, but when it tries to initialize ruby class, debugger disconnect with message Fast Debugger (ruby-debug-ide 0.4.9) listens on :54749 Exception in DebugThread loop: undefined method `is_binary_data?' for "#<HelloWorld:0x85915fc>":String when I set breakpoint to h=HelloWorld.new debugger starts, but after I stepped into initialize() constructor, it disconnects with previous

Is there any command either in debugger or ruby-debug to get a list of all gems and/or plugins loaded in memory for a Rails process? I understand only the ' require ' gems are loaded but I would like to quickly see what got loaded during runtime. This should get you everything loaded through rubygems: Gem.loaded_specs.keys I don't know of a universal way to see which rails plugins are loaded, you can look at the source for Rails::Initializer (pre 3.0) & figure out what your version of rails is doing. Hopefully you know which plugins should be loading & can confirm that from the console when

Does anyone know of a way to run the ruby debugger and SSL at the same time with Thin? I've been using Thin successfully with Rails 3.0.10. I start it using rails server --debugger , and I can debug my code. Recently, I have also needed to add SSL support to my application, and I'd like to be able to test it locally with a self-signed certificate. Unfortunately, I have not found a way to start Thin with SSL support when using rails server . I can successfully start Thin with SSL support by using: thin start --ssl --ssl-verify --ssl-key-file ssllocal/server.key --ssl-cert-file ssllocal/server

I'm having trouble installing the Ruby-Debug Gem on windows. What does this error mean? How can I fix this? Thanks C:\Users\Steve>gem install ruby-debug Building native extensions. This could take a while... ERROR: Error installing ruby-debug: ERROR: Failed to build gem native extension. C:/Ruby19/bin/ruby.exe extconf.rb Can't handle 1.9.x yet *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir -