Triggernig the debugger
in [Ruby]
|
From: Ralph Shnelvar on 15 Jul 2010 15:47 In Rails I can use the debugger statement to trigger the debugger. How can I do that in rdebug? Is there a way other than setting breakpoints manually when the program starts?
From: Ralph Shnelvar on 15 Jul 2010 16:05 Thursday, July 15, 2010, 1:47:08 PM, you wrote: RS> In Rails I can use the RS> debugger RS> statement to trigger the debugger. RS> How can I do that in rdebug? Is there a way other than setting breakpoints manually when the program starts? I found http://bashdb.sourceforge.net/ruby-debug.html#SEC18 and then placed require 'rubygems' require 'ruby-debug into the source ... but I still can't get the debugger to trigger. I get the following messages ... f:\UltraDedup>ruby -r debug UltraDedup.rb Debug.rb Emacs support available. UltraDedup.rb:3:require 'fox16' (rdb:1) c F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/rational.rb:78: `undefined method `gcd' for Rational(1, 2):Rational' (NoMethodError) from F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/yaml.rb:396:in `require' from F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/yaml.rb:396 from UltraDedup.rb:4:in `require' from UltraDedup.rb:4 F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/rational.rb:78: gcd = num.gcd(den) (rdb:1) c F:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/ruby-debug-0.9.3/cli/ruby-debug/processor.rb:17: warning: method redefined; discarding old interface= F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/debug.rb:945 DEBUGGER__.context.trace_func event, file, line, id, binding, klass (rdb:1) Any thoughts on how to trigger the debugger?
From: Robert Dober on 15 Jul 2010 16:16 On Thu, Jul 15, 2010 at 10:15 PM, Robert Dober <robert.dober(a)gmail.com> wrote: > On Thu, Jul 15, 2010 at 10:05 PM, Ralph Shnelvar <ralphs(a)dos32.com> wrote: >> Thursday, July 15, 2010, 1:47:08 PM, you wrote: >> >> RS> In Rails I can use the >> RS> debugger >> RS> statement to trigger the debugger. >> >> RS> How can I do that in rdebug? Is there a way other than setting breakpoints manually when the program starts? >> >> I found >> http://bashdb.sourceforge.net/ruby-debug.html#SEC18 >> and then placed >> >> require 'rubygems' >> require 'ruby-debug >> >> into the source ... >> >> but I still can't get the debugger to trigger. I get the following messages ... >> >> >> f:\UltraDedup>ruby -r debug UltraDedup.rb >> Debug.rb >> Emacs support available. >> >> UltraDedup.rb:3:require 'fox16' >> (rdb:1) c >> F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/rational.rb:78: `undefined method `gcd' for Rational(1, 2):Rational' (NoMethodError) >> from F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/yaml.rb:396:in `require' >> from F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/yaml.rb:396 >> from UltraDedup.rb:4:in `require' >> from UltraDedup.rb:4 >> F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/rational.rb:78: gcd = num.gcd(den) >> (rdb:1) c >> F:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/ruby-debug-0.9.3/cli/ruby-debug/processor.rb:17: warning: method redefined; discarding old interface= >> F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/debug.rb:945 DEBUGGER__.context.trace_func event, file, line, id, binding, klass >> (rdb:1) >> >> >> >> Any thoughts on how to trigger the debugger? > Exactly as you did, then you hit c for continue and that was what the > debugger did > try help to see how to step, trace, set breakpoints and some more > HTH > R. >> >> >> >> >> > > > > -- > The best way to predict the future is to invent it. > -- Alan Kay > -- The best way to predict the future is to invent it. -- Alan Kay
From: Robert Dober on 15 Jul 2010 16:22 On Thu, Jul 15, 2010 at 10:05 PM, Ralph Shnelvar <ralphs(a)dos32.com> wrote: > Thursday, July 15, 2010, 1:47:08 PM, you wrote: > > RS> In Rails I can use the > RS> debugger > RS> statement to trigger the debugger. > > RS> How can I do that in rdebug? Is there a way other than setting breakpoints manually when the program starts? > > I found > http://bashdb.sourceforge.net/ruby-debug.html#SEC18 > and then placed > > require 'rubygems' > require 'ruby-debug > > into the source ... > > but I still can't get the debugger to trigger. I get the following messages ... > > > f:\UltraDedup>ruby -r debug UltraDedup.rb > Debug.rb > Emacs support available. > > UltraDedup.rb:3:require 'fox16' > (rdb:1) c > F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/rational.rb:78: `undefined method `gcd' for Rational(1, 2):Rational' (NoMethodError) > from F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/yaml.rb:396:in `require' > from F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/yaml.rb:396 > from UltraDedup.rb:4:in `require' > from UltraDedup.rb:4 > F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/rational.rb:78: gcd = num.gcd(den) > (rdb:1) c > F:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/ruby-debug-0.9.3/cli/ruby-debug/processor.rb:17: warning: method redefined; discarding old interface= > F:/InstantRails-2.0-win/ruby/lib/ruby/1.8/debug.rb:945 DEBUGGER__.contexttrace_func event, file, line, id, binding, klass > (rdb:1) > > > > Any thoughts on how to trigger the debugger? Exactly as you did, then you hit c for continue and that was what the debugger did try help to see how to step, trace, set breakpoints and some more HTH R. > > > > > -- The best way to predict the future is to invent it. -- Alan Kay
|
Pages: 1 Prev: Think i just figured it out Next: String#to_ptr w/ Ruby 1.9's DL library is undefined |