You can pass the spec file to mspec itself like: mspec run core/io/popen_close
Then I make a call to "debugger" http://gist.github.com/61605, which breaks on a call to System::Diagnostics::Debugger when a debugger is attached to the app. Unfortunately this breaks in a Ruby method, so you have to jump up a couple CLR frames to get to the line directly after the "debugger" call, and I'm not sure of a way how to do that automatically. Anyway, this works great. ~js From: [email protected] [mailto:[email protected]] On Behalf Of Pete Bacon Darwin Sent: Wednesday, February 18, 2009 8:11 AM To: 'Pete Bacon Darwin'; [email protected] Subject: Re: [Ironruby-core] Debugging rubyspecs The easiest way it appears is to stick a pause in the rubyspec of interest and attach to the process while it is waiting. It does totally kill the computer performance while you are debugging (like minutes to step through each line!) Pete From: Pete Bacon Darwin [mailto:[email protected]] Sent: Wednesday,18 February 18, 2009 15:19 To: '[email protected]' Subject: Debugging rubyspecs Anybody know how to run rubyspecs under the Visual Studio debugger? If I just set the rubyspec file as the command line argument in the debug properties in VS then it just asks me to install mspec as a gem. Pete
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
