rubinius

Comments and changes to this ticket

• 

  Brian Ford April 19th, 2008 @ 10:51 PM

  • → State changed from “new” to “resolved”

  The DebugAction in MSpec uses Kernel.debugger provided by the Rubinius debugger. A similar facility is not readily available in MRI. However there are a couple workarounds:

  bin/mspec -tr -T "-rdebug" spec/ruby/1.8/core/numeric/quo_spec.rb
  

  will start the MRI debugger at the beginning. You can then set a breakpoint at a line in that spec file.

  Another option is to set a breakpoint at mspec/runner/actions/debug.rb:5 and step into the spec if the condition evaluates to true.

  It seems a low priority to be able to debug a spec in MRI since the specs are being written to describe already implemented behavior, while in Rubinius and other implementations, a debugger could be useful in trying to figure out why a spec fails.

  I'll accept a patch for a more integrated MRI solution that does not adversely alter how DebugAction presently works, but it's too low priority for me to work on this myself.

  Closing this ticket for now. Please reopen if you have a patch for this facility.