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?
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?
Thursday, July 15, 2010, 1:47:08 PM, you wrote:
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?
I found
ruby-debug
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?
Thursday, July 15, 2010, 1:47:08 PM, you wrote:
> 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?
I found
ruby-debug
and then placedrequire 'rubygems'
require 'ruby-debuginto 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.
On Thu, Jul 15, 2010 at 10:05 PM, Ralph Shnelvar <ralphs@dos32.com> wrote:
--
The best way to predict the future is to invent it.
-- Alan Kay
Thursday, July 15, 2010, 1:47:08 PM, you wrote:
> 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?
I found
ruby-debug
and then placedrequire 'rubygems'
require 'ruby-debuginto 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
On Thu, Jul 15, 2010 at 10:15 PM, Robert Dober <robert.dober@gmail.com> wrote:
On Thu, Jul 15, 2010 at 10:05 PM, Ralph Shnelvar <ralphs@dos32.com> wrote:
--
The best way to predict the future is to invent it.
-- Alan Kay