thr3ads.net - Ironruby core - [Ironruby-core] Debugging rubyspecs [Feb 2009]

If this information is useful, please help other people find it:
Share via:

Pete Bacon Darwin

2009-Feb-18 15:19 UTC

[Ironruby-core] 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090218/5c7de749/attachment.html>

Pete Bacon Darwin

2009-Feb-18 16:11 UTC

head link

[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:bacondarwin at googlemail.com] 
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090218/1316a6cc/attachment-0001.html>

Jimmy Schementi

2009-Feb-18 16:51 UTC

head link

[Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090218/9ef4fc31/attachment.html>

Shri Borde

2009-Feb-18 17:58 UTC

head link

[Ironruby-core] Debugging rubyspecs

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the wiki.

Debugging with Visual Studio
In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows:

 *   Start Action: For Ruby.Console.csproj, "Start project" should be
enabled.
For any other project, "Start external program:" should be enabled and
set to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

 *   Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb:
-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsub_spec.rb
Hitting F5 should now run the single RubySpec example under VS


Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090218/276a570f/attachment.html>

Tomas Matousek

2009-Feb-18 18:25 UTC

head link

[Ironruby-core] Debugging rubyspecs

Do you pass -D to the ir.exe that runs the specs? The debugging is better that
way, although I admit it is not good at all in any case :(

Tomas

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090218/3a033eeb/attachment-0001.html>

Pete Bacon Darwin

2009-Feb-19 14:21 UTC

head link

[Ironruby-core] Debugging rubyspecs

Hi Shri and Jimmy,

 

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

 

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius)
for each test run.  So there is no point in debugging the initial process.

 

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

 

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the
wiki.

 

Debugging with Visual Studio

In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows: 

*	Start Action: For Ruby.Console.csproj, "Start project" should be
enabled. 

For any other project, "Start external program:" should be enabled and
set
to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

*	Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb: 

-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsu
b_spec.rb 

Hitting F5 should now run the single RubySpec example under VS

 

 

Thanks,

Shri

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

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: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com] 
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090219/26a50691/attachment.html>

Jim Deville

2009-Feb-19 18:09 UTC

head link

[Ironruby-core] Debugging rubyspecs

All the versions that IronRuby has used, have the outer layer CRuby process kick
off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also sets
RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

Now that ir -e works (I will be pushing the new revision today), these variables
will affect the operation of the specs. Many of the specs that test top level
code, depend on testing a fresh process, or test the command line options (I am
adding these right now) use the ruby_exe helper. This helper starts a new
process of the currently running implementation to run the specified command or
file. Using the outer layer with -t and -T ensures that these specs are run on
the proper implementation and options. I know that the implementation attempts
to be inferred via other means (RUBY_NAME, RUBY_PLATFORM), but the options are
not as easily taken care of.

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to get
things set up, and if you set things up correctly (using ~/.mspecrc and setting
/path/to/mspec/bin in your PATH) you can run a spec file as easily as mspec ci
core/array/pack (to run core/array/pack_spec.rb). You have to make sure set
:target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec" are set in ~/.mspecrc, from there it should just
work.

Let me know if you have more questions on any of this.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri and Jimmy,

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius) for
each test run.  So there is no point in debugging the initial process.

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the wiki.

Debugging with Visual Studio
In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows:

 *   Start Action: For Ruby.Console.csproj, "Start project" should be
enabled.
For any other project, "Start external program:" should be enabled and
set to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

 *   Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb:
-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsub_spec.rb
Hitting F5 should now run the single RubySpec example under VS


Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090219/2f2b508c/attachment-0001.html>

Shri Borde

2009-Feb-19 18:24 UTC

head link

[Ironruby-core] Debugging rubyspecs

The following command runs a single spec, and only launches ir.exe once. Note
that the command launches mspec-run.rb which does not spawn any processes. The
other runners like mspec-ci etc do spawn a new process for mspec-run.rb.

c:\vsl\Merlin\Main>c:\vsl\Merlin\Main\bin\debug\ir.exe -v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"caches" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/language/regexp_spec.rb

Also, note that in my previous command line, I had an extra "1.8".
This was needed for an earlier version of mspec, but should not be used anymore.
I have updated the wiki with the latest instructions that I have verified work
for me and allow me to hit a breakpoint where I expect.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri and Jimmy,

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius) for
each test run.  So there is no point in debugging the initial process.

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the wiki.

Debugging with Visual Studio
In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows:

 *   Start Action: For Ruby.Console.csproj, "Start project" should be
enabled.
For any other project, "Start external program:" should be enabled and
set to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

 *   Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb:
-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsub_spec.rb
Hitting F5 should now run the single RubySpec example under VS


Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090219/89d35fce/attachment.html>

Pete Bacon Darwin

2009-Feb-19 18:50 UTC

head link

[Ironruby-core] Debugging rubyspecs

I am still having problems with this...

 

D:\dev\ruby\ironruby\current\Merlin\Main>
D:\dev\ruby\ironruby\current\Merlin\Main\bin\debug\ir.exe -v -X:Interpret
d:/dev/ruby/mspec/bin/mspec-run -e "caches" -fs -V -B
"c:/Documents and
Settings/pete/default.mspec" d:/dev/ruby/rubyspec/lang

uage/regexp_spec.rb

unknown: Unable to find a suitable ruby executable. (Exception)

 

Even this has the same result...

 

D:\dev\ruby\ironruby\current\Merlin\Main>d:\dev\ruby\ironruby\current\Merlin
\Main\bin\debug\ir.exe -v -X:Interpret d:/dev/ruby/mspec/bin/mspec-run

unknown: Unable to find a suitable ruby executable. (Exception)

 

Don''t have time to delve into this at the moment but will do so
tomorrow.

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Thursday,19 February 19, 2009 18:24
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

The following command runs a single spec, and only launches ir.exe once.
Note that the command launches mspec-run.rb which does not spawn any
processes. The other runners like mspec-ci etc do spawn a new process for
mspec-run.rb.

 

c:\vsl\Merlin\Main>c:\vsl\Merlin\Main\bin\debug\ir.exe -v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"caches" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/language/regexp_spe
c.rb

 

Also, note that in my previous command line, I had an extra "1.8".
This was
needed for an earlier version of mspec, but should not be used anymore. I
have updated the wiki with the latest instructions that I have verified work
for me and allow me to hit a breakpoint where I expect.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090219/91738de8/attachment-0001.html>

Pete Bacon Darwin

2009-Feb-22 09:28 UTC

head link

[Ironruby-core] Debugging rubyspecs

OK so I worked it out.

 

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant
called RUBY_EXE but it is not able to do so:  It tries to guess it from
various environment, constant and config settings.  Since ir does not set
RUBY_NAME you have to do something like set the environment variable
RUBY_EXE or have a ~/.mspecrc file that specifies the :target => ... and so
on.

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

All the versions that IronRuby has used, have the outer layer CRuby process
kick off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the
specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

 

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also
sets RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

 

Now that ir -e works (I will be pushing the new revision today), these
variables will affect the operation of the specs. Many of the specs that
test top level code, depend on testing a fresh process, or test the command
line options (I am adding these right now) use the ruby_exe helper. This
helper starts a new process of the currently running implementation to run
the specified command or file. Using the outer layer with -t and -T ensures
that these specs are run on the proper implementation and options. I know
that the implementation attempts to be inferred via other means (RUBY_NAME,
RUBY_PLATFORM), but the options are not as easily taken care of. 

 

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to
get things set up, and if you set things up correctly (using ~/.mspecrc and
setting /path/to/mspec/bin in your PATH) you can run a spec file as easily
as mspec ci core/array/pack (to run core/array/pack_spec.rb). You have to
make sure set :target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec"
are set in ~/.mspecrc, from there it should just work.

 

Let me know if you have more questions on any of this.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Hi Shri and Jimmy,

 

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

 

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius)
for each test run.  So there is no point in debugging the initial process.

 

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

 

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the
wiki.

 

Debugging with Visual Studio

In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows: 

*	Start Action: For Ruby.Console.csproj, "Start project" should be
enabled. 

For any other project, "Start external program:" should be enabled and
set
to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

*	Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb: 

-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsu
b_spec.rb 

Hitting F5 should now run the single RubySpec example under VS

 

 

Thanks,

Shri

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

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: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com] 
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090222/1f3db773/attachment-0001.html>

Shri Borde

2009-Feb-23 07:09 UTC

head link

[Ironruby-core] Debugging rubyspecs

I did have to play with a bunch of settings to get mspec to work under VS, and
its possible that I have set some setting that I am now forgetting, but I do not
have RUBY_EXE set, and I don''t seem to have a .mspecrc file either.
Could you please update http://wiki.github.com/ironruby/ironruby with the exact
step you took to enable you to debug with VS so that others don''t have
to go through the same issues?

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK so I worked it out.

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant called
RUBY_EXE but it is not able to do so:  It tries to guess it from various
environment, constant and config settings.  Since ir does not set RUBY_NAME you
have to do something like set the environment variable RUBY_EXE or have a
~/.mspecrc file that specifies the :target => ... and so on.

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

All the versions that IronRuby has used, have the outer layer CRuby process kick
off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also sets
RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

Now that ir -e works (I will be pushing the new revision today), these variables
will affect the operation of the specs. Many of the specs that test top level
code, depend on testing a fresh process, or test the command line options (I am
adding these right now) use the ruby_exe helper. This helper starts a new
process of the currently running implementation to run the specified command or
file. Using the outer layer with -t and -T ensures that these specs are run on
the proper implementation and options. I know that the implementation attempts
to be inferred via other means (RUBY_NAME, RUBY_PLATFORM), but the options are
not as easily taken care of.

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to get
things set up, and if you set things up correctly (using ~/.mspecrc and setting
/path/to/mspec/bin in your PATH) you can run a spec file as easily as mspec ci
core/array/pack (to run core/array/pack_spec.rb). You have to make sure set
:target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec" are set in ~/.mspecrc, from there it should just
work.

Let me know if you have more questions on any of this.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri and Jimmy,

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius) for
each test run.  So there is no point in debugging the initial process.

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the wiki.

Debugging with Visual Studio
In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows:

 *   Start Action: For Ruby.Console.csproj, "Start project" should be
enabled.
For any other project, "Start external program:" should be enabled and
set to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

 *   Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb:
-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsub_spec.rb
Hitting F5 should now run the single RubySpec example under VS


Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090222/dd49f9a2/attachment-0001.html>

Jim Deville

2009-Feb-23 08:00 UTC

head link

[Ironruby-core] Debugging rubyspecs

In my opinion, the most future proof way is going to be using the standard
runner (mspec) and a sleep, or using Jimmy''s debugger wrapper.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Sunday, February 22, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I did have to play with a bunch of settings to get mspec to work under VS, and
its possible that I have set some setting that I am now forgetting, but I do not
have RUBY_EXE set, and I don''t seem to have a .mspecrc file either.
Could you please update http://wiki.github.com/ironruby/ironruby with the exact
step you took to enable you to debug with VS so that others don''t have
to go through the same issues?

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK so I worked it out.

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant called
RUBY_EXE but it is not able to do so:  It tries to guess it from various
environment, constant and config settings.  Since ir does not set RUBY_NAME you
have to do something like set the environment variable RUBY_EXE or have a
~/.mspecrc file that specifies the :target => ... and so on.

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

All the versions that IronRuby has used, have the outer layer CRuby process kick
off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also sets
RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

Now that ir -e works (I will be pushing the new revision today), these variables
will affect the operation of the specs. Many of the specs that test top level
code, depend on testing a fresh process, or test the command line options (I am
adding these right now) use the ruby_exe helper. This helper starts a new
process of the currently running implementation to run the specified command or
file. Using the outer layer with -t and -T ensures that these specs are run on
the proper implementation and options. I know that the implementation attempts
to be inferred via other means (RUBY_NAME, RUBY_PLATFORM), but the options are
not as easily taken care of.

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to get
things set up, and if you set things up correctly (using ~/.mspecrc and setting
/path/to/mspec/bin in your PATH) you can run a spec file as easily as mspec ci
core/array/pack (to run core/array/pack_spec.rb). You have to make sure set
:target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec" are set in ~/.mspecrc, from there it should just
work.

Let me know if you have more questions on any of this.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri and Jimmy,

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius) for
each test run.  So there is no point in debugging the initial process.

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the wiki.

Debugging with Visual Studio
In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows:

 *   Start Action: For Ruby.Console.csproj, "Start project" should be
enabled.
For any other project, "Start external program:" should be enabled and
set to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

 *   Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb:
-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsub_spec.rb
Hitting F5 should now run the single RubySpec example under VS

Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090223/fb53b48f/attachment-0001.html>

Shri Borde

2009-Feb-23 08:51 UTC

head link

[Ironruby-core] Debugging rubyspecs

The convenience of being able to hit F5 in an existing VS session and getting to
the breakpoint you have previously set will be worth the pain of setting it up
for some folks. With mspec and Jimmy''s wrapper (which is also
documented on the wiki), you have to edit the Ruby files you are debugging
(which will require doing "tf edit" first), will launch a new VS
session which can be slow, won''t allow setting conditional breakpoints
easily, wont show unexpected exceptions prior to the sleep/attach which might be
triggering a failure later on, etc. Having options is a good thing so people can
chose whatever works best for them.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Monday, February 23, 2009 12:00 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

In my opinion, the most future proof way is going to be using the standard
runner (mspec) and a sleep, or using Jimmy''s debugger wrapper.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Sunday, February 22, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I did have to play with a bunch of settings to get mspec to work under VS, and
its possible that I have set some setting that I am now forgetting, but I do not
have RUBY_EXE set, and I don''t seem to have a .mspecrc file either.
Could you please update http://wiki.github.com/ironruby/ironruby with the exact
step you took to enable you to debug with VS so that others don''t have
to go through the same issues?

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK so I worked it out.

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant called
RUBY_EXE but it is not able to do so:  It tries to guess it from various
environment, constant and config settings.  Since ir does not set RUBY_NAME you
have to do something like set the environment variable RUBY_EXE or have a
~/.mspecrc file that specifies the :target => ... and so on.

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

All the versions that IronRuby has used, have the outer layer CRuby process kick
off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also sets
RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

Now that ir -e works (I will be pushing the new revision today), these variables
will affect the operation of the specs. Many of the specs that test top level
code, depend on testing a fresh process, or test the command line options (I am
adding these right now) use the ruby_exe helper. This helper starts a new
process of the currently running implementation to run the specified command or
file. Using the outer layer with -t and -T ensures that these specs are run on
the proper implementation and options. I know that the implementation attempts
to be inferred via other means (RUBY_NAME, RUBY_PLATFORM), but the options are
not as easily taken care of.

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to get
things set up, and if you set things up correctly (using ~/.mspecrc and setting
/path/to/mspec/bin in your PATH) you can run a spec file as easily as mspec ci
core/array/pack (to run core/array/pack_spec.rb). You have to make sure set
:target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec" are set in ~/.mspecrc, from there it should just
work.

Let me know if you have more questions on any of this.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri and Jimmy,

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius) for
each test run.  So there is no point in debugging the initial process.

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the wiki.

Debugging with Visual Studio
In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows:

 *   Start Action: For Ruby.Console.csproj, "Start project" should be
enabled.
For any other project, "Start external program:" should be enabled and
set to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

 *   Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb:
-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsub_spec.rb
Hitting F5 should now run the single RubySpec example under VS


Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090223/20116dd9/attachment-0001.html>

Pete Bacon Darwin

2009-Feb-23 14:56 UTC

head link

[Ironruby-core] Debugging rubyspecs

I have updated the wiki.  Let me know if this doesn''t make sense or
doesn''t
work for someone...

http://wiki.github.com/ironruby/ironruby

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Monday,23 February 23, 2009 08:52
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

The convenience of being able to hit F5 in an existing VS session and
getting to the breakpoint you have previously set will be worth the pain of
setting it up for some folks. With mspec and Jimmy''s wrapper (which is
also
documented on the wiki), you have to edit the Ruby files you are debugging
(which will require doing "tf edit" first), will launch a new VS
session
which can be slow, won''t allow setting conditional breakpoints easily,
wont
show unexpected exceptions prior to the sleep/attach which might be
triggering a failure later on, etc. Having options is a good thing so people
can chose whatever works best for them.

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Monday, February 23, 2009 12:00 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

In my opinion, the most future proof way is going to be using the standard
runner (mspec) and a sleep, or using Jimmy''s debugger wrapper.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Sunday, February 22, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I did have to play with a bunch of settings to get mspec to work under VS,
and its possible that I have set some setting that I am now forgetting, but
I do not have RUBY_EXE set, and I don''t seem to have a .mspecrc file
either.
Could you please update http://wiki.github.com/ironruby/ironruby with the
exact step you took to enable you to debug with VS so that others don''t
have
to go through the same issues?

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

OK so I worked it out.

 

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant
called RUBY_EXE but it is not able to do so:  It tries to guess it from
various environment, constant and config settings.  Since ir does not set
RUBY_NAME you have to do something like set the environment variable
RUBY_EXE or have a ~/.mspecrc file that specifies the :target => ... and so
on.

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

All the versions that IronRuby has used, have the outer layer CRuby process
kick off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the
specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

 

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also
sets RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

 

Now that ir -e works (I will be pushing the new revision today), these
variables will affect the operation of the specs. Many of the specs that
test top level code, depend on testing a fresh process, or test the command
line options (I am adding these right now) use the ruby_exe helper. This
helper starts a new process of the currently running implementation to run
the specified command or file. Using the outer layer with -t and -T ensures
that these specs are run on the proper implementation and options. I know
that the implementation attempts to be inferred via other means (RUBY_NAME,
RUBY_PLATFORM), but the options are not as easily taken care of. 

 

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to
get things set up, and if you set things up correctly (using ~/.mspecrc and
setting /path/to/mspec/bin in your PATH) you can run a spec file as easily
as mspec ci core/array/pack (to run core/array/pack_spec.rb). You have to
make sure set :target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec"
are set in ~/.mspecrc, from there it should just work.

 

Let me know if you have more questions on any of this.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Hi Shri and Jimmy,

 

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

 

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius)
for each test run.  So there is no point in debugging the initial process.

 

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

 

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the
wiki.

 

Debugging with Visual Studio

In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows: 

*	Start Action: For Ruby.Console.csproj, "Start project" should be
enabled. 

For any other project, "Start external program:" should be enabled and
set
to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

*	Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb: 

-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsu
b_spec.rb 

Hitting F5 should now run the single RubySpec example under VS

 

 

Thanks,

Shri

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

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: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com] 
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090223/939f57b8/attachment-0001.html>

Shri Borde

2009-Feb-23 18:13 UTC

head link

[Ironruby-core] Debugging rubyspecs

That is a comprehensive description!

Its unfortunate it has to be as complex. Ideally, mspec-run will take all
arguments (like the ruby executable) on the command line which will increase
discoverability. But for now, the workarounds will do.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 6:56 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I have updated the wiki.  Let me know if this doesn''t make sense or
doesn''t work for someone...
http://wiki.github.com/ironruby/ironruby

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Monday,23 February 23, 2009 08:52
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

The convenience of being able to hit F5 in an existing VS session and getting to
the breakpoint you have previously set will be worth the pain of setting it up
for some folks. With mspec and Jimmy''s wrapper (which is also
documented on the wiki), you have to edit the Ruby files you are debugging
(which will require doing "tf edit" first), will launch a new VS
session which can be slow, won''t allow setting conditional breakpoints
easily, wont show unexpected exceptions prior to the sleep/attach which might be
triggering a failure later on, etc. Having options is a good thing so people can
chose whatever works best for them.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Monday, February 23, 2009 12:00 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

In my opinion, the most future proof way is going to be using the standard
runner (mspec) and a sleep, or using Jimmy''s debugger wrapper.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Sunday, February 22, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I did have to play with a bunch of settings to get mspec to work under VS, and
its possible that I have set some setting that I am now forgetting, but I do not
have RUBY_EXE set, and I don''t seem to have a .mspecrc file either.
Could you please update http://wiki.github.com/ironruby/ironruby with the exact
step you took to enable you to debug with VS so that others don''t have
to go through the same issues?

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK so I worked it out.

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant called
RUBY_EXE but it is not able to do so:  It tries to guess it from various
environment, constant and config settings.  Since ir does not set RUBY_NAME you
have to do something like set the environment variable RUBY_EXE or have a
~/.mspecrc file that specifies the :target => ... and so on.

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

All the versions that IronRuby has used, have the outer layer CRuby process kick
off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also sets
RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

Now that ir -e works (I will be pushing the new revision today), these variables
will affect the operation of the specs. Many of the specs that test top level
code, depend on testing a fresh process, or test the command line options (I am
adding these right now) use the ruby_exe helper. This helper starts a new
process of the currently running implementation to run the specified command or
file. Using the outer layer with -t and -T ensures that these specs are run on
the proper implementation and options. I know that the implementation attempts
to be inferred via other means (RUBY_NAME, RUBY_PLATFORM), but the options are
not as easily taken care of.

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to get
things set up, and if you set things up correctly (using ~/.mspecrc and setting
/path/to/mspec/bin in your PATH) you can run a spec file as easily as mspec ci
core/array/pack (to run core/array/pack_spec.rb). You have to make sure set
:target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec" are set in ~/.mspecrc, from there it should just
work.

Let me know if you have more questions on any of this.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri and Jimmy,

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius) for
each test run.  So there is no point in debugging the initial process.

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the wiki.

Debugging with Visual Studio
In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows:

 *   Start Action: For Ruby.Console.csproj, "Start project" should be
enabled.
For any other project, "Start external program:" should be enabled and
set to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

 *   Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb:
-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsub_spec.rb
Hitting F5 should now run the single RubySpec example under VS

Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090223/b6ab3caf/attachment-0001.html>

Jim Deville

2009-Feb-23 18:20 UTC

head link

[Ironruby-core] Debugging rubyspecs

I made some corrections and added a point:

*         Mspec doesn''t spawn each spec under a new process, just the
mspec-run command. This doesn''t prevent corruption of specs, which is
why there is the conflicts_with guard. It''s also why you should run
core before library specs if you are doing a full run (Complex conflicts with
most Numeric subclasses).

*         If you are setting RUBY_EXE, you should also set RUBY_FLAGS. The
latter is the options passed to the implementation, and sense you are suggesting
adding -X:Interpret to the command, you''ll want RUBY_FLAGS set to
"-X:Interpret", so that the specs run under ruby_exe get the correct
runner.

*         We should also figure out how to debug a spec that uses ruby_exe and
add that to the wiki. It will probably come down to translating the ruby_exe
method into the command line that gets called, but there might be another way.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 6:56 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I have updated the wiki.  Let me know if this doesn''t make sense or
doesn''t work for someone...
http://wiki.github.com/ironruby/ironruby

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Monday,23 February 23, 2009 08:52
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

The convenience of being able to hit F5 in an existing VS session and getting to
the breakpoint you have previously set will be worth the pain of setting it up
for some folks. With mspec and Jimmy''s wrapper (which is also
documented on the wiki), you have to edit the Ruby files you are debugging
(which will require doing "tf edit" first), will launch a new VS
session which can be slow, won''t allow setting conditional breakpoints
easily, wont show unexpected exceptions prior to the sleep/attach which might be
triggering a failure later on, etc. Having options is a good thing so people can
chose whatever works best for them.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Monday, February 23, 2009 12:00 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

In my opinion, the most future proof way is going to be using the standard
runner (mspec) and a sleep, or using Jimmy''s debugger wrapper.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Sunday, February 22, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I did have to play with a bunch of settings to get mspec to work under VS, and
its possible that I have set some setting that I am now forgetting, but I do not
have RUBY_EXE set, and I don''t seem to have a .mspecrc file either.
Could you please update http://wiki.github.com/ironruby/ironruby with the exact
step you took to enable you to debug with VS so that others don''t have
to go through the same issues?

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK so I worked it out.

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant called
RUBY_EXE but it is not able to do so:  It tries to guess it from various
environment, constant and config settings.  Since ir does not set RUBY_NAME you
have to do something like set the environment variable RUBY_EXE or have a
~/.mspecrc file that specifies the :target => ... and so on.

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

All the versions that IronRuby has used, have the outer layer CRuby process kick
off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also sets
RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

Now that ir -e works (I will be pushing the new revision today), these variables
will affect the operation of the specs. Many of the specs that test top level
code, depend on testing a fresh process, or test the command line options (I am
adding these right now) use the ruby_exe helper. This helper starts a new
process of the currently running implementation to run the specified command or
file. Using the outer layer with -t and -T ensures that these specs are run on
the proper implementation and options. I know that the implementation attempts
to be inferred via other means (RUBY_NAME, RUBY_PLATFORM), but the options are
not as easily taken care of.

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to get
things set up, and if you set things up correctly (using ~/.mspecrc and setting
/path/to/mspec/bin in your PATH) you can run a spec file as easily as mspec ci
core/array/pack (to run core/array/pack_spec.rb). You have to make sure set
:target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec" are set in ~/.mspecrc, from there it should just
work.

Let me know if you have more questions on any of this.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri and Jimmy,

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius) for
each test run.  So there is no point in debugging the initial process.

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the wiki.

Debugging with Visual Studio
In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows:

 *   Start Action: For Ruby.Console.csproj, "Start project" should be
enabled.
For any other project, "Start external program:" should be enabled and
set to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

 *   Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb:
-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsub_spec.rb
Hitting F5 should now run the single RubySpec example under VS


Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090223/42a950bf/attachment-0001.html>

Jim Deville

2009-Feb-23 19:00 UTC

head link

[Ironruby-core] Debugging rubyspecs

Well, mspec takes all the arguments on the command line. I wouldn''t
want to specify all of the options 2x. Once as the runner, and once as
arguments.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Monday, February 23, 2009 10:13 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

That is a comprehensive description!

Its unfortunate it has to be as complex. Ideally, mspec-run will take all
arguments (like the ruby executable) on the command line which will increase
discoverability. But for now, the workarounds will do.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 6:56 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I have updated the wiki.  Let me know if this doesn''t make sense or
doesn''t work for someone...
http://wiki.github.com/ironruby/ironruby

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Monday,23 February 23, 2009 08:52
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

The convenience of being able to hit F5 in an existing VS session and getting to
the breakpoint you have previously set will be worth the pain of setting it up
for some folks. With mspec and Jimmy''s wrapper (which is also
documented on the wiki), you have to edit the Ruby files you are debugging
(which will require doing "tf edit" first), will launch a new VS
session which can be slow, won''t allow setting conditional breakpoints
easily, wont show unexpected exceptions prior to the sleep/attach which might be
triggering a failure later on, etc. Having options is a good thing so people can
chose whatever works best for them.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Monday, February 23, 2009 12:00 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

In my opinion, the most future proof way is going to be using the standard
runner (mspec) and a sleep, or using Jimmy''s debugger wrapper.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Sunday, February 22, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I did have to play with a bunch of settings to get mspec to work under VS, and
its possible that I have set some setting that I am now forgetting, but I do not
have RUBY_EXE set, and I don''t seem to have a .mspecrc file either.
Could you please update http://wiki.github.com/ironruby/ironruby with the exact
step you took to enable you to debug with VS so that others don''t have
to go through the same issues?

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK so I worked it out.

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant called
RUBY_EXE but it is not able to do so:  It tries to guess it from various
environment, constant and config settings.  Since ir does not set RUBY_NAME you
have to do something like set the environment variable RUBY_EXE or have a
~/.mspecrc file that specifies the :target => ... and so on.

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

All the versions that IronRuby has used, have the outer layer CRuby process kick
off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also sets
RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

Now that ir -e works (I will be pushing the new revision today), these variables
will affect the operation of the specs. Many of the specs that test top level
code, depend on testing a fresh process, or test the command line options (I am
adding these right now) use the ruby_exe helper. This helper starts a new
process of the currently running implementation to run the specified command or
file. Using the outer layer with -t and -T ensures that these specs are run on
the proper implementation and options. I know that the implementation attempts
to be inferred via other means (RUBY_NAME, RUBY_PLATFORM), but the options are
not as easily taken care of.

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to get
things set up, and if you set things up correctly (using ~/.mspecrc and setting
/path/to/mspec/bin in your PATH) you can run a spec file as easily as mspec ci
core/array/pack (to run core/array/pack_spec.rb). You have to make sure set
:target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec" are set in ~/.mspecrc, from there it should just
work.

Let me know if you have more questions on any of this.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri and Jimmy,

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius) for
each test run.  So there is no point in debugging the initial process.

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the wiki.

Debugging with Visual Studio
In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows:

 *   Start Action: For Ruby.Console.csproj, "Start project" should be
enabled.
For any other project, "Start external program:" should be enabled and
set to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

 *   Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb:
-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsub_spec.rb
Hitting F5 should now run the single RubySpec example under VS

Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090223/08c0d624/attachment-0001.html>

Pete Bacon Darwin

2009-Feb-23 20:34 UTC

head link

[Ironruby-core] Debugging rubyspecs

Sadly I don''t think that mspec-run looks at the standard command line
options for specifying the target implementation.  I tried specifying set
:target, ... in my ~/.mspecrc file but it didn''t help.

 

To be honest, this is really a bug in mspec-run.  It should not actually
require ruby_exe.rb at all as it doesn''t use it.  It should only really
be
used when it is spawning off new processes.

 

There is an alternative solution which requires a change to the rbconfig.rb
file inside the standard libraries.  The ruby_exe.rb file will look into
this configuration class and pull out the following to calculate the path to
the ruby exectuble.

 

      bin = Config::CONFIG["RUBY_INSTALL_NAME"] ||
Config::CONFIG["ruby_install_name"]

      bin << (Config::CONFIG[''EXEEXT''] ||
Config::CONFIG[''exeext''] || '''')

      File.join(Config::CONFIG[''bindir''], bin)

 

If the version of rbconfig.rb that is shipped with IronRuby was correctly
set up then this would work automatically for everyone.  This is exactly how
the standard MRI version works when it requires ruby_exe.rb.

 

Currently the version of rbconfig.rb that is included via the ir.exe.config
is found in Merlin/Main/Languages/Ruby/Libs/rbconfig.rb and specifies the
following:

 

  # TODO: Temporary hack to locate where we are based on relative MERLIN

  # layout paths. We will replace this with just the path to this file when

  # we build out the Ruby/libs directory to contain our own private copy of 

  # the Ruby libraries

  # Note that this symbol should be redefined by the packaging script for
binary

  # layouts  TOPDIR = File.dirname(__FILE__) +
''/../../../../External/languages/ruby/ruby-1.8.6/''

  CONFIG["prefix"] = (TOPDIR || DESTDIR + "")

  CONFIG["exec_prefix"] = "$(prefix)"

  CONFIG["bindir"] = "$(exec_prefix)/bin"

  # TODO: change back to ironruby

  CONFIG["ruby_install_name"] = "ruby"

  CONFIG["RUBY_INSTALL_NAME"] = "ruby"

  # END TODO:

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Monday,23 February 23, 2009 19:00
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Well, mspec takes all the arguments on the command line. I wouldn''t
want to
specify all of the options 2x. Once as the runner, and once as arguments.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Monday, February 23, 2009 10:13 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

That is a comprehensive description! 

 

Its unfortunate it has to be as complex. Ideally, mspec-run will take all
arguments (like the ruby executable) on the command line which will increase
discoverability. But for now, the workarounds will do.

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 6:56 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I have updated the wiki.  Let me know if this doesn''t make sense or
doesn''t
work for someone...

http://wiki.github.com/ironruby/ironruby

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Monday,23 February 23, 2009 08:52
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

The convenience of being able to hit F5 in an existing VS session and
getting to the breakpoint you have previously set will be worth the pain of
setting it up for some folks. With mspec and Jimmy''s wrapper (which is
also
documented on the wiki), you have to edit the Ruby files you are debugging
(which will require doing "tf edit" first), will launch a new VS
session
which can be slow, won''t allow setting conditional breakpoints easily,
wont
show unexpected exceptions prior to the sleep/attach which might be
triggering a failure later on, etc. Having options is a good thing so people
can chose whatever works best for them.

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Monday, February 23, 2009 12:00 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

In my opinion, the most future proof way is going to be using the standard
runner (mspec) and a sleep, or using Jimmy''s debugger wrapper.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Sunday, February 22, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I did have to play with a bunch of settings to get mspec to work under VS,
and its possible that I have set some setting that I am now forgetting, but
I do not have RUBY_EXE set, and I don''t seem to have a .mspecrc file
either.
Could you please update http://wiki.github.com/ironruby/ironruby with the
exact step you took to enable you to debug with VS so that others don''t
have
to go through the same issues?

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

OK so I worked it out.

 

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant
called RUBY_EXE but it is not able to do so:  It tries to guess it from
various environment, constant and config settings.  Since ir does not set
RUBY_NAME you have to do something like set the environment variable
RUBY_EXE or have a ~/.mspecrc file that specifies the :target => ... and so
on.

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

All the versions that IronRuby has used, have the outer layer CRuby process
kick off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the
specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

 

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also
sets RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

 

Now that ir -e works (I will be pushing the new revision today), these
variables will affect the operation of the specs. Many of the specs that
test top level code, depend on testing a fresh process, or test the command
line options (I am adding these right now) use the ruby_exe helper. This
helper starts a new process of the currently running implementation to run
the specified command or file. Using the outer layer with -t and -T ensures
that these specs are run on the proper implementation and options. I know
that the implementation attempts to be inferred via other means (RUBY_NAME,
RUBY_PLATFORM), but the options are not as easily taken care of. 

 

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to
get things set up, and if you set things up correctly (using ~/.mspecrc and
setting /path/to/mspec/bin in your PATH) you can run a spec file as easily
as mspec ci core/array/pack (to run core/array/pack_spec.rb). You have to
make sure set :target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec"
are set in ~/.mspecrc, from there it should just work.

 

Let me know if you have more questions on any of this.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Hi Shri and Jimmy,

 

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

 

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius)
for each test run.  So there is no point in debugging the initial process.

 

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

 

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the
wiki.

 

Debugging with Visual Studio

In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows: 

*	Start Action: For Ruby.Console.csproj, "Start project" should be
enabled. 

For any other project, "Start external program:" should be enabled and
set
to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

*	Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb: 

-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsu
b_spec.rb 

Hitting F5 should now run the single RubySpec example under VS

 

 

Thanks,

Shri

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

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: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com] 
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090223/e3b79625/attachment-0001.html>

Jim Deville

2009-Feb-23 22:29 UTC

head link

[Ironruby-core] Debugging rubyspecs

Yeah, that is correct. -t and -T, and set :target are used by MSpec, not
mspec-run (and it''s sibling scripts).

As for not using ruby_exe, it is used in various specs, and all of the command
line specs I am writing. It''s not directly required by mspec-run, it
gets required during the loading of the rest of mspec. I feel that ruby_exe is
part of MSpec, just like should, the matchers, and the other helpers.

I agree that it would be nice to get rbconfig set up correctly, in addition to
RUBY_NAME.  However, it does appear that RUBY_NAME is set to RUBY_ENGINE if
RUBY_NAME isn''t defined.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 12:34 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Sadly I don''t think that mspec-run looks at the standard command line
options for specifying the target implementation.  I tried specifying set
:target, ... in my ~/.mspecrc file but it didn''t help.

To be honest, this is really a bug in mspec-run.  It should not actually require
ruby_exe.rb at all as it doesn''t use it.  It should only really be used
when it is spawning off new processes.

There is an alternative solution which requires a change to the rbconfig.rb file
inside the standard libraries.  The ruby_exe.rb file will look into this
configuration class and pull out the following to calculate the path to the ruby
exectuble.

      bin = Config::CONFIG["RUBY_INSTALL_NAME"] ||
Config::CONFIG["ruby_install_name"]
      bin << (Config::CONFIG[''EXEEXT''] ||
Config::CONFIG[''exeext''] || '''')
      File.join(Config::CONFIG[''bindir''], bin)

If the version of rbconfig.rb that is shipped with IronRuby was correctly set up
then this would work automatically for everyone.  This is exactly how the
standard MRI version works when it requires ruby_exe.rb.

Currently the version of rbconfig.rb that is included via the ir.exe.config is
found in Merlin/Main/Languages/Ruby/Libs/rbconfig.rb and specifies the
following:

  # TODO: Temporary hack to locate where we are based on relative MERLIN
  # layout paths. We will replace this with just the path to this file when
  # we build out the Ruby/libs directory to contain our own private copy of
  # the Ruby libraries
  # Note that this symbol should be redefined by the packaging script for binary
  # layouts  TOPDIR = File.dirname(__FILE__) +
''/../../../../External/languages/ruby/ruby-1.8.6/''
  CONFIG["prefix"] = (TOPDIR || DESTDIR + "")
  CONFIG["exec_prefix"] = "$(prefix)"
  CONFIG["bindir"] = "$(exec_prefix)/bin"
  # TODO: change back to ironruby
  CONFIG["ruby_install_name"] = "ruby"
  CONFIG["RUBY_INSTALL_NAME"] = "ruby"
  # END TODO:

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Monday,23 February 23, 2009 19:00
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Well, mspec takes all the arguments on the command line. I wouldn''t
want to specify all of the options 2x. Once as the runner, and once as
arguments.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Monday, February 23, 2009 10:13 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

That is a comprehensive description!

Its unfortunate it has to be as complex. Ideally, mspec-run will take all
arguments (like the ruby executable) on the command line which will increase
discoverability. But for now, the workarounds will do.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 6:56 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I have updated the wiki.  Let me know if this doesn''t make sense or
doesn''t work for someone...
http://wiki.github.com/ironruby/ironruby

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Monday,23 February 23, 2009 08:52
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

The convenience of being able to hit F5 in an existing VS session and getting to
the breakpoint you have previously set will be worth the pain of setting it up
for some folks. With mspec and Jimmy''s wrapper (which is also
documented on the wiki), you have to edit the Ruby files you are debugging
(which will require doing "tf edit" first), will launch a new VS
session which can be slow, won''t allow setting conditional breakpoints
easily, wont show unexpected exceptions prior to the sleep/attach which might be
triggering a failure later on, etc. Having options is a good thing so people can
chose whatever works best for them.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Monday, February 23, 2009 12:00 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

In my opinion, the most future proof way is going to be using the standard
runner (mspec) and a sleep, or using Jimmy''s debugger wrapper.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Sunday, February 22, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I did have to play with a bunch of settings to get mspec to work under VS, and
its possible that I have set some setting that I am now forgetting, but I do not
have RUBY_EXE set, and I don''t seem to have a .mspecrc file either.
Could you please update http://wiki.github.com/ironruby/ironruby with the exact
step you took to enable you to debug with VS so that others don''t have
to go through the same issues?

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK so I worked it out.

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant called
RUBY_EXE but it is not able to do so:  It tries to guess it from various
environment, constant and config settings.  Since ir does not set RUBY_NAME you
have to do something like set the environment variable RUBY_EXE or have a
~/.mspecrc file that specifies the :target => ... and so on.

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

All the versions that IronRuby has used, have the outer layer CRuby process kick
off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also sets
RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

Now that ir -e works (I will be pushing the new revision today), these variables
will affect the operation of the specs. Many of the specs that test top level
code, depend on testing a fresh process, or test the command line options (I am
adding these right now) use the ruby_exe helper. This helper starts a new
process of the currently running implementation to run the specified command or
file. Using the outer layer with -t and -T ensures that these specs are run on
the proper implementation and options. I know that the implementation attempts
to be inferred via other means (RUBY_NAME, RUBY_PLATFORM), but the options are
not as easily taken care of.

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to get
things set up, and if you set things up correctly (using ~/.mspecrc and setting
/path/to/mspec/bin in your PATH) you can run a spec file as easily as mspec ci
core/array/pack (to run core/array/pack_spec.rb). You have to make sure set
:target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec" are set in ~/.mspecrc, from there it should just
work.

Let me know if you have more questions on any of this.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri and Jimmy,

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius) for
each test run.  So there is no point in debugging the initial process.

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the wiki.

Debugging with Visual Studio
In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows:

 *   Start Action: For Ruby.Console.csproj, "Start project" should be
enabled.
For any other project, "Start external program:" should be enabled and
set to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

 *   Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb:
-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsub_spec.rb
Hitting F5 should now run the single RubySpec example under VS


Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090223/9e860ceb/attachment-0001.html>

Pete Bacon Darwin

2009-Feb-24 07:20 UTC

head link

[Ironruby-core] Debugging rubyspecs

Oops yeah I forgot that ruby_exe is probably used in some of the rubyspecs.
How about we knock up a small ruby file that sets everything up and passes
through to mspec-run that we can just run directly without any command line
arguments from VS debugger?

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Monday,23 February 23, 2009 22:29
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Yeah, that is correct. -t and -T, and set :target are used by MSpec, not
mspec-run (and it''s sibling scripts). 

 

As for not using ruby_exe, it is used in various specs, and all of the
command line specs I am writing. It''s not directly required by
mspec-run, it
gets required during the loading of the rest of mspec. I feel that ruby_exe
is part of MSpec, just like should, the matchers, and the other helpers. 

 

I agree that it would be nice to get rbconfig set up correctly, in addition
to RUBY_NAME.  However, it does appear that RUBY_NAME is set to RUBY_ENGINE
if RUBY_NAME isn''t defined.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 12:34 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Sadly I don''t think that mspec-run looks at the standard command line
options for specifying the target implementation.  I tried specifying set
:target, ... in my ~/.mspecrc file but it didn''t help.

 

To be honest, this is really a bug in mspec-run.  It should not actually
require ruby_exe.rb at all as it doesn''t use it.  It should only really
be
used when it is spawning off new processes.

 

There is an alternative solution which requires a change to the rbconfig.rb
file inside the standard libraries.  The ruby_exe.rb file will look into
this configuration class and pull out the following to calculate the path to
the ruby exectuble.

 

      bin = Config::CONFIG["RUBY_INSTALL_NAME"] ||
Config::CONFIG["ruby_install_name"]

      bin << (Config::CONFIG[''EXEEXT''] ||
Config::CONFIG[''exeext''] || '''')

      File.join(Config::CONFIG[''bindir''], bin)

 

If the version of rbconfig.rb that is shipped with IronRuby was correctly
set up then this would work automatically for everyone.  This is exactly how
the standard MRI version works when it requires ruby_exe.rb.

 

Currently the version of rbconfig.rb that is included via the ir.exe.config
is found in Merlin/Main/Languages/Ruby/Libs/rbconfig.rb and specifies the
following:

 

  # TODO: Temporary hack to locate where we are based on relative MERLIN

  # layout paths. We will replace this with just the path to this file when

  # we build out the Ruby/libs directory to contain our own private copy of 

  # the Ruby libraries

  # Note that this symbol should be redefined by the packaging script for
binary

  # layouts  TOPDIR = File.dirname(__FILE__) +
''/../../../../External/languages/ruby/ruby-1.8.6/''

  CONFIG["prefix"] = (TOPDIR || DESTDIR + "")

  CONFIG["exec_prefix"] = "$(prefix)"

  CONFIG["bindir"] = "$(exec_prefix)/bin"

  # TODO: change back to ironruby

  CONFIG["ruby_install_name"] = "ruby"

  CONFIG["RUBY_INSTALL_NAME"] = "ruby"

  # END TODO:

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Monday,23 February 23, 2009 19:00
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Well, mspec takes all the arguments on the command line. I wouldn''t
want to
specify all of the options 2x. Once as the runner, and once as arguments.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Monday, February 23, 2009 10:13 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

That is a comprehensive description! 

 

Its unfortunate it has to be as complex. Ideally, mspec-run will take all
arguments (like the ruby executable) on the command line which will increase
discoverability. But for now, the workarounds will do.

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 6:56 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I have updated the wiki.  Let me know if this doesn''t make sense or
doesn''t
work for someone...

http://wiki.github.com/ironruby/ironruby

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Monday,23 February 23, 2009 08:52
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

The convenience of being able to hit F5 in an existing VS session and
getting to the breakpoint you have previously set will be worth the pain of
setting it up for some folks. With mspec and Jimmy''s wrapper (which is
also
documented on the wiki), you have to edit the Ruby files you are debugging
(which will require doing "tf edit" first), will launch a new VS
session
which can be slow, won''t allow setting conditional breakpoints easily,
wont
show unexpected exceptions prior to the sleep/attach which might be
triggering a failure later on, etc. Having options is a good thing so people
can chose whatever works best for them.

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Monday, February 23, 2009 12:00 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

In my opinion, the most future proof way is going to be using the standard
runner (mspec) and a sleep, or using Jimmy''s debugger wrapper.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Sunday, February 22, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I did have to play with a bunch of settings to get mspec to work under VS,
and its possible that I have set some setting that I am now forgetting, but
I do not have RUBY_EXE set, and I don''t seem to have a .mspecrc file
either.
Could you please update http://wiki.github.com/ironruby/ironruby with the
exact step you took to enable you to debug with VS so that others don''t
have
to go through the same issues?

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

OK so I worked it out.

 

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant
called RUBY_EXE but it is not able to do so:  It tries to guess it from
various environment, constant and config settings.  Since ir does not set
RUBY_NAME you have to do something like set the environment variable
RUBY_EXE or have a ~/.mspecrc file that specifies the :target => ... and so
on.

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

All the versions that IronRuby has used, have the outer layer CRuby process
kick off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the
specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

 

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also
sets RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

 

Now that ir -e works (I will be pushing the new revision today), these
variables will affect the operation of the specs. Many of the specs that
test top level code, depend on testing a fresh process, or test the command
line options (I am adding these right now) use the ruby_exe helper. This
helper starts a new process of the currently running implementation to run
the specified command or file. Using the outer layer with -t and -T ensures
that these specs are run on the proper implementation and options. I know
that the implementation attempts to be inferred via other means (RUBY_NAME,
RUBY_PLATFORM), but the options are not as easily taken care of. 

 

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to
get things set up, and if you set things up correctly (using ~/.mspecrc and
setting /path/to/mspec/bin in your PATH) you can run a spec file as easily
as mspec ci core/array/pack (to run core/array/pack_spec.rb). You have to
make sure set :target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec"
are set in ~/.mspecrc, from there it should just work.

 

Let me know if you have more questions on any of this.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Hi Shri and Jimmy,

 

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

 

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius)
for each test run.  So there is no point in debugging the initial process.

 

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

 

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the
wiki.

 

Debugging with Visual Studio

In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows: 

*	Start Action: For Ruby.Console.csproj, "Start project" should be
enabled. 

For any other project, "Start external program:" should be enabled and
set
to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

*	Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb: 

-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsu
b_spec.rb 

Hitting F5 should now run the single RubySpec example under VS

 

 

Thanks,

Shri

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

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: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com] 
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090224/76af79a9/attachment-0001.html>

Jim Deville

2009-Feb-24 07:30 UTC

head link

[Ironruby-core] Debugging rubyspecs

So something that does what mspec does, without the new process? I wonder if we
could just make mspec not spawn a new process if the running Ruby is the same as
the target ruby. We would still need to pass -T and -t, thus specifying the args
2x, but I think that it is better than maintaining a separate script if
something changes in MSpec.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 11:21 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Oops yeah I forgot that ruby_exe is probably used in some of the rubyspecs.  How
about we knock up a small ruby file that sets everything up and passes through
to mspec-run that we can just run directly without any command line arguments
from VS debugger?

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Monday,23 February 23, 2009 22:29
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Yeah, that is correct. -t and -T, and set :target are used by MSpec, not
mspec-run (and it''s sibling scripts).

As for not using ruby_exe, it is used in various specs, and all of the command
line specs I am writing. It''s not directly required by mspec-run, it
gets required during the loading of the rest of mspec. I feel that ruby_exe is
part of MSpec, just like should, the matchers, and the other helpers.

I agree that it would be nice to get rbconfig set up correctly, in addition to
RUBY_NAME.  However, it does appear that RUBY_NAME is set to RUBY_ENGINE if
RUBY_NAME isn''t defined.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 12:34 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Sadly I don''t think that mspec-run looks at the standard command line
options for specifying the target implementation.  I tried specifying set
:target, ... in my ~/.mspecrc file but it didn''t help.

To be honest, this is really a bug in mspec-run.  It should not actually require
ruby_exe.rb at all as it doesn''t use it.  It should only really be used
when it is spawning off new processes.

There is an alternative solution which requires a change to the rbconfig.rb file
inside the standard libraries.  The ruby_exe.rb file will look into this
configuration class and pull out the following to calculate the path to the ruby
exectuble.

      bin = Config::CONFIG["RUBY_INSTALL_NAME"] ||
Config::CONFIG["ruby_install_name"]
      bin << (Config::CONFIG[''EXEEXT''] ||
Config::CONFIG[''exeext''] || '''')
      File.join(Config::CONFIG[''bindir''], bin)

If the version of rbconfig.rb that is shipped with IronRuby was correctly set up
then this would work automatically for everyone.  This is exactly how the
standard MRI version works when it requires ruby_exe.rb.

Currently the version of rbconfig.rb that is included via the ir.exe.config is
found in Merlin/Main/Languages/Ruby/Libs/rbconfig.rb and specifies the
following:

  # TODO: Temporary hack to locate where we are based on relative MERLIN
  # layout paths. We will replace this with just the path to this file when
  # we build out the Ruby/libs directory to contain our own private copy of
  # the Ruby libraries
  # Note that this symbol should be redefined by the packaging script for binary
  # layouts  TOPDIR = File.dirname(__FILE__) +
''/../../../../External/languages/ruby/ruby-1.8.6/''
  CONFIG["prefix"] = (TOPDIR || DESTDIR + "")
  CONFIG["exec_prefix"] = "$(prefix)"
  CONFIG["bindir"] = "$(exec_prefix)/bin"
  # TODO: change back to ironruby
  CONFIG["ruby_install_name"] = "ruby"
  CONFIG["RUBY_INSTALL_NAME"] = "ruby"
  # END TODO:

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Monday,23 February 23, 2009 19:00
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Well, mspec takes all the arguments on the command line. I wouldn''t
want to specify all of the options 2x. Once as the runner, and once as
arguments.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Monday, February 23, 2009 10:13 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

That is a comprehensive description!

Its unfortunate it has to be as complex. Ideally, mspec-run will take all
arguments (like the ruby executable) on the command line which will increase
discoverability. But for now, the workarounds will do.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 6:56 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I have updated the wiki.  Let me know if this doesn''t make sense or
doesn''t work for someone...
http://wiki.github.com/ironruby/ironruby

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Monday,23 February 23, 2009 08:52
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

The convenience of being able to hit F5 in an existing VS session and getting to
the breakpoint you have previously set will be worth the pain of setting it up
for some folks. With mspec and Jimmy''s wrapper (which is also
documented on the wiki), you have to edit the Ruby files you are debugging
(which will require doing "tf edit" first), will launch a new VS
session which can be slow, won''t allow setting conditional breakpoints
easily, wont show unexpected exceptions prior to the sleep/attach which might be
triggering a failure later on, etc. Having options is a good thing so people can
chose whatever works best for them.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Monday, February 23, 2009 12:00 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

In my opinion, the most future proof way is going to be using the standard
runner (mspec) and a sleep, or using Jimmy''s debugger wrapper.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Sunday, February 22, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I did have to play with a bunch of settings to get mspec to work under VS, and
its possible that I have set some setting that I am now forgetting, but I do not
have RUBY_EXE set, and I don''t seem to have a .mspecrc file either.
Could you please update http://wiki.github.com/ironruby/ironruby with the exact
step you took to enable you to debug with VS so that others don''t have
to go through the same issues?

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK so I worked it out.

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant called
RUBY_EXE but it is not able to do so:  It tries to guess it from various
environment, constant and config settings.  Since ir does not set RUBY_NAME you
have to do something like set the environment variable RUBY_EXE or have a
~/.mspecrc file that specifies the :target => ... and so on.

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

All the versions that IronRuby has used, have the outer layer CRuby process kick
off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also sets
RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

Now that ir -e works (I will be pushing the new revision today), these variables
will affect the operation of the specs. Many of the specs that test top level
code, depend on testing a fresh process, or test the command line options (I am
adding these right now) use the ruby_exe helper. This helper starts a new
process of the currently running implementation to run the specified command or
file. Using the outer layer with -t and -T ensures that these specs are run on
the proper implementation and options. I know that the implementation attempts
to be inferred via other means (RUBY_NAME, RUBY_PLATFORM), but the options are
not as easily taken care of.

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to get
things set up, and if you set things up correctly (using ~/.mspecrc and setting
/path/to/mspec/bin in your PATH) you can run a spec file as easily as mspec ci
core/array/pack (to run core/array/pack_spec.rb). You have to make sure set
:target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec" are set in ~/.mspecrc, from there it should just
work.

Let me know if you have more questions on any of this.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri and Jimmy,

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius) for
each test run.  So there is no point in debugging the initial process.

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the wiki.

Debugging with Visual Studio
In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows:

 *   Start Action: For Ruby.Console.csproj, "Start project" should be
enabled.
For any other project, "Start external program:" should be enabled and
set to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

 *   Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb:
-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsub_spec.rb
Hitting F5 should now run the single RubySpec example under VS


Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

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: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com]
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090223/5f572483/attachment-0001.html>

Pete Bacon Darwin

2009-Feb-24 08:02 UTC

head link

[Ironruby-core] Debugging rubyspecs

I might be wrong but all the command line arguments can be monkey patched in
by defining a MSpecScript class like in default.mspec type file.

So what I am suggesting is that we knock up a mspec-debug.rb file that sets
up the MSpecScript class and also defines RUBY_EXE constant and then runs
the MSpecRun class.

I think then the only command line item would be the specs to run...

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Tuesday,24 February 24, 2009 07:31
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

So something that does what mspec does, without the new process? I wonder if
we could just make mspec not spawn a new process if the running Ruby is the
same as the target ruby. We would still need to pass -T and -t, thus
specifying the args 2x, but I think that it is better than maintaining a
separate script if something changes in MSpec.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 11:21 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Oops yeah I forgot that ruby_exe is probably used in some of the rubyspecs.
How about we knock up a small ruby file that sets everything up and passes
through to mspec-run that we can just run directly without any command line
arguments from VS debugger?

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Monday,23 February 23, 2009 22:29
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Yeah, that is correct. -t and -T, and set :target are used by MSpec, not
mspec-run (and it''s sibling scripts). 

 

As for not using ruby_exe, it is used in various specs, and all of the
command line specs I am writing. It''s not directly required by
mspec-run, it
gets required during the loading of the rest of mspec. I feel that ruby_exe
is part of MSpec, just like should, the matchers, and the other helpers. 

 

I agree that it would be nice to get rbconfig set up correctly, in addition
to RUBY_NAME.  However, it does appear that RUBY_NAME is set to RUBY_ENGINE
if RUBY_NAME isn''t defined.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 12:34 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Sadly I don''t think that mspec-run looks at the standard command line
options for specifying the target implementation.  I tried specifying set
:target, ... in my ~/.mspecrc file but it didn''t help.

 

To be honest, this is really a bug in mspec-run.  It should not actually
require ruby_exe.rb at all as it doesn''t use it.  It should only really
be
used when it is spawning off new processes.

 

There is an alternative solution which requires a change to the rbconfig.rb
file inside the standard libraries.  The ruby_exe.rb file will look into
this configuration class and pull out the following to calculate the path to
the ruby exectuble.

 

      bin = Config::CONFIG["RUBY_INSTALL_NAME"] ||
Config::CONFIG["ruby_install_name"]

      bin << (Config::CONFIG[''EXEEXT''] ||
Config::CONFIG[''exeext''] || '''')

      File.join(Config::CONFIG[''bindir''], bin)

 

If the version of rbconfig.rb that is shipped with IronRuby was correctly
set up then this would work automatically for everyone.  This is exactly how
the standard MRI version works when it requires ruby_exe.rb.

 

Currently the version of rbconfig.rb that is included via the ir.exe.config
is found in Merlin/Main/Languages/Ruby/Libs/rbconfig.rb and specifies the
following:

 

  # TODO: Temporary hack to locate where we are based on relative MERLIN

  # layout paths. We will replace this with just the path to this file when

  # we build out the Ruby/libs directory to contain our own private copy of 

  # the Ruby libraries

  # Note that this symbol should be redefined by the packaging script for
binary

  # layouts  TOPDIR = File.dirname(__FILE__) +
''/../../../../External/languages/ruby/ruby-1.8.6/''

  CONFIG["prefix"] = (TOPDIR || DESTDIR + "")

  CONFIG["exec_prefix"] = "$(prefix)"

  CONFIG["bindir"] = "$(exec_prefix)/bin"

  # TODO: change back to ironruby

  CONFIG["ruby_install_name"] = "ruby"

  CONFIG["RUBY_INSTALL_NAME"] = "ruby"

  # END TODO:

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Monday,23 February 23, 2009 19:00
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Well, mspec takes all the arguments on the command line. I wouldn''t
want to
specify all of the options 2x. Once as the runner, and once as arguments.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Monday, February 23, 2009 10:13 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

That is a comprehensive description! 

 

Its unfortunate it has to be as complex. Ideally, mspec-run will take all
arguments (like the ruby executable) on the command line which will increase
discoverability. But for now, the workarounds will do.

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Monday, February 23, 2009 6:56 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I have updated the wiki.  Let me know if this doesn''t make sense or
doesn''t
work for someone...

http://wiki.github.com/ironruby/ironruby

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Monday,23 February 23, 2009 08:52
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

The convenience of being able to hit F5 in an existing VS session and
getting to the breakpoint you have previously set will be worth the pain of
setting it up for some folks. With mspec and Jimmy''s wrapper (which is
also
documented on the wiki), you have to edit the Ruby files you are debugging
(which will require doing "tf edit" first), will launch a new VS
session
which can be slow, won''t allow setting conditional breakpoints easily,
wont
show unexpected exceptions prior to the sleep/attach which might be
triggering a failure later on, etc. Having options is a good thing so people
can chose whatever works best for them.

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Monday, February 23, 2009 12:00 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

In my opinion, the most future proof way is going to be using the standard
runner (mspec) and a sleep, or using Jimmy''s debugger wrapper.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Sunday, February 22, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I did have to play with a bunch of settings to get mspec to work under VS,
and its possible that I have set some setting that I am now forgetting, but
I do not have RUBY_EXE set, and I don''t seem to have a .mspecrc file
either.
Could you please update http://wiki.github.com/ironruby/ironruby with the
exact step you took to enable you to debug with VS so that others don''t
have
to go through the same issues?

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Sunday, February 22, 2009 1:29 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

OK so I worked it out.

 

Mspec-run does indeed run only a single process but it still requires
mspec/lib/mspec/helpers/ruby_exe.rb.  This file tries to set a constant
called RUBY_EXE but it is not able to do so:  It tries to guess it from
various environment, constant and config settings.  Since ir does not set
RUBY_NAME you have to do something like set the environment variable
RUBY_EXE or have a ~/.mspecrc file that specifies the :target => ... and so
on.

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,19 February 19, 2009 18:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

All the versions that IronRuby has used, have the outer layer CRuby process
kick off a target implementation process. If you call mspec -fs core -t
"ir.exe", it becomes a call to ir.exe mspec-run -fs core. For many of
the
specs, you can skip the outer layer, and run mspec-run (or mspec-ci, or
mspec-tag) directly. For debugging, this is what Shri is talking about.

 

As a side note, I advise not doing it this way in general, since there are
environment variables set via the outer layer runner, which will affect the
operation of Mspec. Until now, it has only been MSPEC_RUNNER=1, which tells
Mspec that the specs are being run by Mspec, not Rspec. However, Mspec also
sets RUBY_EXE and RUBY_OPTIONS, to the values of the -t and -T flags.

 

Now that ir -e works (I will be pushing the new revision today), these
variables will affect the operation of the specs. Many of the specs that
test top level code, depend on testing a fresh process, or test the command
line options (I am adding these right now) use the ruby_exe helper. This
helper starts a new process of the currently running implementation to run
the specified command or file. Using the outer layer with -t and -T ensures
that these specs are run on the proper implementation and options. I know
that the implementation attempts to be inferred via other means (RUBY_NAME,
RUBY_PLATFORM), but the options are not as easily taken care of. 

 

The wiki (http://wiki.github.com/ironruby/ironruby/rubyspec) tells how to
get things set up, and if you set things up correctly (using ~/.mspecrc and
setting /path/to/mspec/bin in your PATH) you can run a spec file as easily
as mspec ci core/array/pack (to run core/array/pack_spec.rb). You have to
make sure set :target, "/path/to/ir.exe" and set :prefix,
"path/to/rubyspec"
are set in ~/.mspecrc, from there it should just work.

 

Let me know if you have more questions on any of this.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 19, 2009 6:21 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Hi Shri and Jimmy,

 

Thanks for the suggestions.  What version of mspec are you running?  I am
running the head version directly from rubyspecs github: "d482804 Added
should have_constant matcher."

 

In my version, the initial ruby process kicks off a new ruby process
(potentially a completely different implementation, like JRuby or Rubinius)
for each test run.  So there is no point in debugging the initial process.

 

Shri, on my machine your instructions below result in "unknown: Unable to
find a suitable ruby executable. (Exception)", which I guess is mspec
telling me it couldn''t load ir.exe or equivalent as a sub-process for
executing the spec.

 

Jimmy, how do you attach to the mspec process in the first place?  The same
problem as above is true for just debugging mspec run ...

 

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,18 February 18, 2009 17:59
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Here is what I added to http://wiki.github.com/ironruby/ironruby. This works
pretty well for me. If the paths are incorrect, feel free to update the
wiki.

 

Debugging with Visual Studio

In the Debug tab of the Project properties for Ruby.Console.csproj, set the
fields as follows: 

*	Start Action: For Ruby.Console.csproj, "Start project" should be
enabled. 

For any other project, "Start external program:" should be enabled and
set
to "c:\vsl\Merlin\Main\Bin\Debug\ir.exe"

*	Start Options: "Command line arguments" should be set to the
following for running the "supports /i for ignoring case" example of
string\gsub_spec.rb: 

-v -X:Interpret
c:/vsl/Merlin/External/Languages/IronRuby/mspec/mspec/bin/mspec-run -e
"supports /i for ignoring case" -fs -V -B
c:/vsl/Merlin/External/Languages/IronRuby/mspec/default.mspec
c:/vsl/Merlin/External/Languages/IronRuby/mspec/rubyspec/1.8/core/string/gsu
b_spec.rb 

Hitting F5 should now run the single RubySpec example under VS

 

 

Thanks,

Shri

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jimmy Schementi
Sent: Wednesday, February 18, 2009 8:52 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

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: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 18, 2009 8:11 AM
To: ''Pete Bacon Darwin''; ironruby-core at rubyforge.org
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:bacondarwin at googlemail.com] 
Sent: Wednesday,18 February 18, 2009 15:19
To: ''ironruby-core at rubyforge.org''
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090224/c80f7d4c/attachment-0001.html>

Pete Bacon Darwin

2009-Feb-24 11:11 UTC

head link

[Ironruby-core] Debugging rubyspecs

OK, this is what I mean.  I save the following file (attached also) as
Merlin/Main/Languages/Ruby/mspec-debug.rb:

 

RUBY_EXE =
''d:/dev/ruby/ironruby/current/Merlin/Main/Bin/debug/ir.exe''

 

$:.unshift ''d:/dev/ruby/mspec/lib''

 

require ''mspec/commands/mspec-run''

require ''mspec''

 

class MSpecScript

  set :target, RUBY_EXE

  set :flags, [ '' -D'']

  set :ci_files, ["rubyspec/1.8/core",]

  set :tags_patterns, [

    [%r(rubyspec/), ''ironruby-tags/''],

    [/_spec.rb$/, ''_tags.txt'']

  ]

end

 

MSpecRun.main

 

Once you have modified the paths for your setup, you can then run this file
just like mspec-run:

 

/path/to/ir.exe mspec-debug.rb /path/to/rubyspec/some_spec.rb

 

In the VS Ruby.Console project properties I set the following:

 

Start Action: Start Project

Start Options:

       Command Line Options: -D mspec-debug.rb -V
d:/dev/ruby/rubyspec/core/fixnum/abs_spec.rb

       Working Directory:
D:\dev\ruby\ironruby\current\Merlin\Main\Languages\Ruby\

 

Then I can set breakpoints in the C# code to debug and so on.

 

This solution is self contained, doesn''t require any environment
variables,
doesn''t spawn any sub processes and doesn''t rely on mspec
guessing the ruby
engine.  I personally don''t feel that it uses too much of the internals
of
mspec: the configuration bits are public interfaces to mspec and all we are
doing is including a couple of files (that are unlikely to change name) and
running a single class method.

 

Let me know what you think.

Pete

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090224/308208e8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mspec-debug.rb
Type: application/octet-stream
Size: 394 bytes
Desc: not available
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090224/308208e8/attachment.obj>

Shri Borde

2009-Feb-25 21:32 UTC

head link

[Ironruby-core] Debugging rubyspecs

I checked a bit, and I don''t have a RUBY_EXE environment variable, or a
%HOME%\.mspecrc file. Peter, did you use "-B /path/to/default.mspec"
in the ir.exe command-line, and does it set :target? I do have both of these,
and maybe that is why it works for me.

If mspec-debug.rb works for you, sure, you should add a note on the wiki about
it. I would be fine with using either a default.mspec (which already exists) or
a mspec-debug.rb.

Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Tuesday, February 24, 2009 3:11 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK, this is what I mean.  I save the following file (attached also) as
Merlin/Main/Languages/Ruby/mspec-debug.rb:

RUBY_EXE =
''d:/dev/ruby/ironruby/current/Merlin/Main/Bin/debug/ir.exe''

$:.unshift ''d:/dev/ruby/mspec/lib''

require ''mspec/commands/mspec-run''
require ''mspec''

class MSpecScript
  set :target, RUBY_EXE
  set :flags, [ '' -D'']
  set :ci_files, ["rubyspec/1.8/core",]
  set :tags_patterns, [
    [%r(rubyspec/), ''ironruby-tags/''],
    [/_spec.rb$/, ''_tags.txt'']
  ]
end

MSpecRun.main

Once you have modified the paths for your setup, you can then run this file just
like mspec-run:

/path/to/ir.exe mspec-debug.rb /path/to/rubyspec/some_spec.rb

In the VS Ruby.Console project properties I set the following:

Start Action: Start Project
Start Options:
       Command Line Options: -D mspec-debug.rb -V
d:/dev/ruby/rubyspec/core/fixnum/abs_spec.rb
       Working Directory:
D:\dev\ruby\ironruby\current\Merlin\Main\Languages\Ruby\

Then I can set breakpoints in the C# code to debug and so on.

This solution is self contained, doesn''t require any environment
variables, doesn''t spawn any sub processes and doesn''t rely on
mspec guessing the ruby engine.  I personally don''t feel that it uses
too much of the internals of mspec: the configuration bits are public interfaces
to mspec and all we are doing is including a couple of files (that are unlikely
to change name) and running a single class method.

Let me know what you think.
Pete
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090225/1f030420/attachment.html>

Pete Bacon Darwin

2009-Feb-26 04:30 UTC

head link

[Ironruby-core] Debugging rubyspecs

Hi Shri,

I tried just using the -B option with this information inside my
default.mspec file but in my install of mspec, the default.mspec never gets
loaded as the ruby_exe.rb is required before the mspec.default file and it
blows up inside ruby_exe.rb.  The reason that mspec-debug.rb works is that
the RUBY_EXE constant is defined before mspec and therefore ruby_exe are
required.

What version of mspec are you running?

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,25 February 25, 2009 21:33
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I checked a bit, and I don''t have a RUBY_EXE environment variable, or a
%HOME%\.mspecrc file. Peter, did you use "-B /path/to/default.mspec"
in the
ir.exe command-line, and does it set :target? I do have both of these, and
maybe that is why it works for me.

 

If mspec-debug.rb works for you, sure, you should add a note on the wiki
about it. I would be fine with using either a default.mspec (which already
exists) or a mspec-debug.rb.

 

Thanks,

Shri

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Tuesday, February 24, 2009 3:11 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

OK, this is what I mean.  I save the following file (attached also) as
Merlin/Main/Languages/Ruby/mspec-debug.rb:

 

RUBY_EXE =
''d:/dev/ruby/ironruby/current/Merlin/Main/Bin/debug/ir.exe''

 

$:.unshift ''d:/dev/ruby/mspec/lib''

 

require ''mspec/commands/mspec-run''

require ''mspec''

 

class MSpecScript

  set :target, RUBY_EXE

  set :flags, [ '' -D'']

  set :ci_files, ["rubyspec/1.8/core",]

  set :tags_patterns, [

    [%r(rubyspec/), ''ironruby-tags/''],

    [/_spec.rb$/, ''_tags.txt'']

  ]

end

 

MSpecRun.main

 

Once you have modified the paths for your setup, you can then run this file
just like mspec-run:

 

/path/to/ir.exe mspec-debug.rb /path/to/rubyspec/some_spec.rb

 

In the VS Ruby.Console project properties I set the following:

 

Start Action: Start Project

Start Options:

       Command Line Options: -D mspec-debug.rb -V
d:/dev/ruby/rubyspec/core/fixnum/abs_spec.rb

       Working Directory:
D:\dev\ruby\ironruby\current\Merlin\Main\Languages\Ruby\

 

Then I can set breakpoints in the C# code to debug and so on.

 

This solution is self contained, doesn''t require any environment
variables,
doesn''t spawn any sub processes and doesn''t rely on mspec
guessing the ruby
engine.  I personally don''t feel that it uses too much of the internals
of
mspec: the configuration bits are public interfaces to mspec and all we are
doing is including a couple of files (that are unlikely to change name) and
running a single class method.

 

Let me know what you think.

Pete

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090226/38cc997e/attachment-0001.html>

Shri Borde

2009-Feb-26 07:08 UTC

head link

[Ironruby-core] Debugging rubyspecs

I am not sure how to describe our version of mspec. I don''t see any
version number in the mspec folder. Jim should confirm, but it must be the one
from http://github.com/ironruby/mspec/tree/master.

Btw, Jim is looking to make it easier to run mspec by adding a .mspecrc file and
some other utility commands. Lets see if that clears this up...

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 25, 2009 8:31 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri,
I tried just using the -B option with this information inside my default.mspec
file but in my install of mspec, the default.mspec never gets loaded as the
ruby_exe.rb is required before the mspec.default file and it blows up inside
ruby_exe.rb.  The reason that mspec-debug.rb works is that the RUBY_EXE constant
is defined before mspec and therefore ruby_exe are required.
What version of mspec are you running?
Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,25 February 25, 2009 21:33
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I checked a bit, and I don''t have a RUBY_EXE environment variable, or a
%HOME%\.mspecrc file. Peter, did you use "-B /path/to/default.mspec"
in the ir.exe command-line, and does it set :target? I do have both of these,
and maybe that is why it works for me.

If mspec-debug.rb works for you, sure, you should add a note on the wiki about
it. I would be fine with using either a default.mspec (which already exists) or
a mspec-debug.rb.

Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Tuesday, February 24, 2009 3:11 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK, this is what I mean.  I save the following file (attached also) as
Merlin/Main/Languages/Ruby/mspec-debug.rb:

RUBY_EXE =
''d:/dev/ruby/ironruby/current/Merlin/Main/Bin/debug/ir.exe''

$:.unshift ''d:/dev/ruby/mspec/lib''

require ''mspec/commands/mspec-run''
require ''mspec''

class MSpecScript
  set :target, RUBY_EXE
  set :flags, [ '' -D'']
  set :ci_files, ["rubyspec/1.8/core",]
  set :tags_patterns, [
    [%r(rubyspec/), ''ironruby-tags/''],
    [/_spec.rb$/, ''_tags.txt'']
  ]
end

MSpecRun.main

Once you have modified the paths for your setup, you can then run this file just
like mspec-run:

/path/to/ir.exe mspec-debug.rb /path/to/rubyspec/some_spec.rb

In the VS Ruby.Console project properties I set the following:

Start Action: Start Project
Start Options:
       Command Line Options: -D mspec-debug.rb -V
d:/dev/ruby/rubyspec/core/fixnum/abs_spec.rb
       Working Directory:
D:\dev\ruby\ironruby\current\Merlin\Main\Languages\Ruby\

Then I can set breakpoints in the C# code to debug and so on.

This solution is self contained, doesn''t require any environment
variables, doesn''t spawn any sub processes and doesn''t rely on
mspec guessing the ruby engine.  I personally don''t feel that it uses
too much of the internals of mspec: the configuration bits are public interfaces
to mspec and all we are doing is including a couple of files (that are unlikely
to change name) and running a single class method.

Let me know what you think.
Pete
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090225/043416d5/attachment-0001.html>

Jim Deville

2009-Feb-26 07:38 UTC

head link

[Ironruby-core] Debugging rubyspecs

The version is some portion of the version 1.5.6 (I don''t know the
exact commit, but that is the version number)(Shri, if you ever need to find
out, it''s in a weird place. Mspec/lib/mspec/version.rb).

As Shri said, after my current task goes through (braving the troll right now),
I will try to make things a little easier and setup files that should get
consumed by default, so you won''t need -B.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday, February 25, 2009 11:09 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I am not sure how to describe our version of mspec. I don''t see any
version number in the mspec folder. Jim should confirm, but it must be the one
from http://github.com/ironruby/mspec/tree/master.

Btw, Jim is looking to make it easier to run mspec by adding a .mspecrc file and
some other utility commands. Lets see if that clears this up...

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 25, 2009 8:31 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri,
I tried just using the -B option with this information inside my default.mspec
file but in my install of mspec, the default.mspec never gets loaded as the
ruby_exe.rb is required before the mspec.default file and it blows up inside
ruby_exe.rb.  The reason that mspec-debug.rb works is that the RUBY_EXE constant
is defined before mspec and therefore ruby_exe are required.
What version of mspec are you running?
Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,25 February 25, 2009 21:33
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I checked a bit, and I don''t have a RUBY_EXE environment variable, or a
%HOME%\.mspecrc file. Peter, did you use "-B /path/to/default.mspec"
in the ir.exe command-line, and does it set :target? I do have both of these,
and maybe that is why it works for me.

If mspec-debug.rb works for you, sure, you should add a note on the wiki about
it. I would be fine with using either a default.mspec (which already exists) or
a mspec-debug.rb.

Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Tuesday, February 24, 2009 3:11 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK, this is what I mean.  I save the following file (attached also) as
Merlin/Main/Languages/Ruby/mspec-debug.rb:

RUBY_EXE =
''d:/dev/ruby/ironruby/current/Merlin/Main/Bin/debug/ir.exe''

$:.unshift ''d:/dev/ruby/mspec/lib''

require ''mspec/commands/mspec-run''
require ''mspec''

class MSpecScript
  set :target, RUBY_EXE
  set :flags, [ '' -D'']
  set :ci_files, ["rubyspec/1.8/core",]
  set :tags_patterns, [
    [%r(rubyspec/), ''ironruby-tags/''],
    [/_spec.rb$/, ''_tags.txt'']
  ]
end

MSpecRun.main

Once you have modified the paths for your setup, you can then run this file just
like mspec-run:

/path/to/ir.exe mspec-debug.rb /path/to/rubyspec/some_spec.rb

In the VS Ruby.Console project properties I set the following:

Start Action: Start Project
Start Options:
       Command Line Options: -D mspec-debug.rb -V
d:/dev/ruby/rubyspec/core/fixnum/abs_spec.rb
       Working Directory:
D:\dev\ruby\ironruby\current\Merlin\Main\Languages\Ruby\

Then I can set breakpoints in the C# code to debug and so on.

This solution is self contained, doesn''t require any environment
variables, doesn''t spawn any sub processes and doesn''t rely on
mspec guessing the ruby engine.  I personally don''t feel that it uses
too much of the internals of mspec: the configuration bits are public interfaces
to mspec and all we are doing is including a couple of files (that are unlikely
to change name) and running a single class method.

Let me know what you think.
Pete
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090225/ccc75338/attachment.html>

Pete Bacon Darwin

2009-Feb-26 07:51 UTC

head link

[Ironruby-core] Debugging rubyspecs

OK so I am running a recent (if not latest) pull from the
github/rubyspec/mspec repository.  May be that is the difference.  Neither
.mspecrc or -B file get loaded before the ruby_exe.rb so neither files will
fix this problem.  The only long term solution is to fix rbconfig.rb.  The
short term one is to set RUBY_EXE as an environment variable or as a ruby
constant before any call to require "mspec".

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Thursday,26 February 26, 2009 07:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I am not sure how to describe our version of mspec. I don''t see any
version
number in the mspec folder. Jim should confirm, but it must be the one from
http://github.com/ironruby/mspec/tree/master. 

 

Btw, Jim is looking to make it easier to run mspec by adding a .mspecrc file
and some other utility commands. Lets see if that clears this up.

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 25, 2009 8:31 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Hi Shri,

I tried just using the -B option with this information inside my
default.mspec file but in my install of mspec, the default.mspec never gets
loaded as the ruby_exe.rb is required before the mspec.default file and it
blows up inside ruby_exe.rb.  The reason that mspec-debug.rb works is that
the RUBY_EXE constant is defined before mspec and therefore ruby_exe are
required.

What version of mspec are you running?

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,25 February 25, 2009 21:33
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I checked a bit, and I don''t have a RUBY_EXE environment variable, or a
%HOME%\.mspecrc file. Peter, did you use "-B /path/to/default.mspec"
in the
ir.exe command-line, and does it set :target? I do have both of these, and
maybe that is why it works for me.

 

If mspec-debug.rb works for you, sure, you should add a note on the wiki
about it. I would be fine with using either a default.mspec (which already
exists) or a mspec-debug.rb.

 

Thanks,

Shri

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Tuesday, February 24, 2009 3:11 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

OK, this is what I mean.  I save the following file (attached also) as
Merlin/Main/Languages/Ruby/mspec-debug.rb:

 

RUBY_EXE =
''d:/dev/ruby/ironruby/current/Merlin/Main/Bin/debug/ir.exe''

 

$:.unshift ''d:/dev/ruby/mspec/lib''

 

require ''mspec/commands/mspec-run''

require ''mspec''

 

class MSpecScript

  set :target, RUBY_EXE

  set :flags, [ '' -D'']

  set :ci_files, ["rubyspec/1.8/core",]

  set :tags_patterns, [

    [%r(rubyspec/), ''ironruby-tags/''],

    [/_spec.rb$/, ''_tags.txt'']

  ]

end

 

MSpecRun.main

 

Once you have modified the paths for your setup, you can then run this file
just like mspec-run:

 

/path/to/ir.exe mspec-debug.rb /path/to/rubyspec/some_spec.rb

 

In the VS Ruby.Console project properties I set the following:

 

Start Action: Start Project

Start Options:

       Command Line Options: -D mspec-debug.rb -V
d:/dev/ruby/rubyspec/core/fixnum/abs_spec.rb

       Working Directory:
D:\dev\ruby\ironruby\current\Merlin\Main\Languages\Ruby\

 

Then I can set breakpoints in the C# code to debug and so on.

 

This solution is self contained, doesn''t require any environment
variables,
doesn''t spawn any sub processes and doesn''t rely on mspec
guessing the ruby
engine.  I personally don''t feel that it uses too much of the internals
of
mspec: the configuration bits are public interfaces to mspec and all we are
doing is including a couple of files (that are unlikely to change name) and
running a single class method.

 

Let me know what you think.

Pete

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090226/86d0cbaf/attachment-0001.html>

Jim Deville

2009-Feb-26 08:14 UTC

head link

[Ironruby-core] Debugging rubyspecs

The other option, which I''ve already asked Brian Ford to do, is to not
find the force the RUBY_EXE evaluation unless the ruby_exe method is called.
That will make it only matter when you want to run a ruby_exe method. It sounds
like there might be another issue, but I''ll look into it.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 25, 2009 11:52 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK so I am running a recent (if not latest) pull from the github/rubyspec/mspec
repository.  May be that is the difference.  Neither .mspecrc or -B file get
loaded before the ruby_exe.rb so neither files will fix this problem.  The only
long term solution is to fix rbconfig.rb.  The short term one is to set RUBY_EXE
as an environment variable or as a ruby constant before any call to require
"mspec".
Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Thursday,26 February 26, 2009 07:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I am not sure how to describe our version of mspec. I don''t see any
version number in the mspec folder. Jim should confirm, but it must be the one
from http://github.com/ironruby/mspec/tree/master.

Btw, Jim is looking to make it easier to run mspec by adding a .mspecrc file and
some other utility commands. Lets see if that clears this up...

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 25, 2009 8:31 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri,
I tried just using the -B option with this information inside my default.mspec
file but in my install of mspec, the default.mspec never gets loaded as the
ruby_exe.rb is required before the mspec.default file and it blows up inside
ruby_exe.rb.  The reason that mspec-debug.rb works is that the RUBY_EXE constant
is defined before mspec and therefore ruby_exe are required.
What version of mspec are you running?
Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,25 February 25, 2009 21:33
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I checked a bit, and I don''t have a RUBY_EXE environment variable, or a
%HOME%\.mspecrc file. Peter, did you use "-B /path/to/default.mspec"
in the ir.exe command-line, and does it set :target? I do have both of these,
and maybe that is why it works for me.

If mspec-debug.rb works for you, sure, you should add a note on the wiki about
it. I would be fine with using either a default.mspec (which already exists) or
a mspec-debug.rb.

Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Tuesday, February 24, 2009 3:11 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK, this is what I mean.  I save the following file (attached also) as
Merlin/Main/Languages/Ruby/mspec-debug.rb:

RUBY_EXE =
''d:/dev/ruby/ironruby/current/Merlin/Main/Bin/debug/ir.exe''

$:.unshift ''d:/dev/ruby/mspec/lib''

require ''mspec/commands/mspec-run''
require ''mspec''

class MSpecScript
  set :target, RUBY_EXE
  set :flags, [ '' -D'']
  set :ci_files, ["rubyspec/1.8/core",]
  set :tags_patterns, [
    [%r(rubyspec/), ''ironruby-tags/''],
    [/_spec.rb$/, ''_tags.txt'']
  ]
end

MSpecRun.main

Once you have modified the paths for your setup, you can then run this file just
like mspec-run:

/path/to/ir.exe mspec-debug.rb /path/to/rubyspec/some_spec.rb

In the VS Ruby.Console project properties I set the following:

Start Action: Start Project
Start Options:
       Command Line Options: -D mspec-debug.rb -V
d:/dev/ruby/rubyspec/core/fixnum/abs_spec.rb
       Working Directory:
D:\dev\ruby\ironruby\current\Merlin\Main\Languages\Ruby\

Then I can set breakpoints in the C# code to debug and so on.

This solution is self contained, doesn''t require any environment
variables, doesn''t spawn any sub processes and doesn''t rely on
mspec guessing the ruby engine.  I personally don''t feel that it uses
too much of the internals of mspec: the configuration bits are public interfaces
to mspec and all we are doing is including a couple of files (that are unlikely
to change name) and running a single class method.

Let me know what you think.
Pete
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090226/acc7f39e/attachment.html>

Pete Bacon Darwin

2009-Feb-26 08:34 UTC

head link

[Ironruby-core] Debugging rubyspecs

Yes, that would be a good idea; then .mspecrc or similar would have been
loaded before ruby_exe gets called.  I think they need to look at the
implementation of resolve_ruby_exe in that class anyway as I don''t
think it
looks at the :target option but I might be wrong.  If that is true then you
will still need to set RUBY_EXE in the .mspecrc or similar file.

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,26 February 26, 2009 08:14
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

The other option, which I''ve already asked Brian Ford to do, is to not
find
the force the RUBY_EXE evaluation unless the ruby_exe method is called. That
will make it only matter when you want to run a ruby_exe method. It sounds
like there might be another issue, but I''ll look into it.

 

JD

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 25, 2009 11:52 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

OK so I am running a recent (if not latest) pull from the
github/rubyspec/mspec repository.  May be that is the difference.  Neither
.mspecrc or -B file get loaded before the ruby_exe.rb so neither files will
fix this problem.  The only long term solution is to fix rbconfig.rb.  The
short term one is to set RUBY_EXE as an environment variable or as a ruby
constant before any call to require "mspec".

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Thursday,26 February 26, 2009 07:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I am not sure how to describe our version of mspec. I don''t see any
version
number in the mspec folder. Jim should confirm, but it must be the one from
http://github.com/ironruby/mspec/tree/master. 

 

Btw, Jim is looking to make it easier to run mspec by adding a .mspecrc file
and some other utility commands. Lets see if that clears this up.

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 25, 2009 8:31 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

Hi Shri,

I tried just using the -B option with this information inside my
default.mspec file but in my install of mspec, the default.mspec never gets
loaded as the ruby_exe.rb is required before the mspec.default file and it
blows up inside ruby_exe.rb.  The reason that mspec-debug.rb works is that
the RUBY_EXE constant is defined before mspec and therefore ruby_exe are
required.

What version of mspec are you running?

Pete

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,25 February 25, 2009 21:33
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

I checked a bit, and I don''t have a RUBY_EXE environment variable, or a
%HOME%\.mspecrc file. Peter, did you use "-B /path/to/default.mspec"
in the
ir.exe command-line, and does it set :target? I do have both of these, and
maybe that is why it works for me.

 

If mspec-debug.rb works for you, sure, you should add a note on the wiki
about it. I would be fine with using either a default.mspec (which already
exists) or a mspec-debug.rb.

 

Thanks,

Shri

 

From: ironruby-core-bounces at rubyforge.org
[mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Tuesday, February 24, 2009 3:11 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

 

OK, this is what I mean.  I save the following file (attached also) as
Merlin/Main/Languages/Ruby/mspec-debug.rb:

 

RUBY_EXE =
''d:/dev/ruby/ironruby/current/Merlin/Main/Bin/debug/ir.exe''

 

$:.unshift ''d:/dev/ruby/mspec/lib''

 

require ''mspec/commands/mspec-run''

require ''mspec''

 

class MSpecScript

  set :target, RUBY_EXE

  set :flags, [ '' -D'']

  set :ci_files, ["rubyspec/1.8/core",]

  set :tags_patterns, [

    [%r(rubyspec/), ''ironruby-tags/''],

    [/_spec.rb$/, ''_tags.txt'']

  ]

end

 

MSpecRun.main

 

Once you have modified the paths for your setup, you can then run this file
just like mspec-run:

 

/path/to/ir.exe mspec-debug.rb /path/to/rubyspec/some_spec.rb

 

In the VS Ruby.Console project properties I set the following:

 

Start Action: Start Project

Start Options:

       Command Line Options: -D mspec-debug.rb -V
d:/dev/ruby/rubyspec/core/fixnum/abs_spec.rb

       Working Directory:
D:\dev\ruby\ironruby\current\Merlin\Main\Languages\Ruby\

 

Then I can set breakpoints in the C# code to debug and so on.

 

This solution is self contained, doesn''t require any environment
variables,
doesn''t spawn any sub processes and doesn''t rely on mspec
guessing the ruby
engine.  I personally don''t feel that it uses too much of the internals
of
mspec: the configuration bits are public interfaces to mspec and all we are
doing is including a couple of files (that are unlikely to change name) and
running a single class method.

 

Let me know what you think.

Pete

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090226/7a7150cc/attachment-0001.html>

Jim Deville

2009-Feb-26 09:05 UTC

head link

[Ironruby-core] Debugging rubyspecs

I think it is currently by design that resolve_ruby_exe doesn''t look at
:target, but it would be a good heuristic to add.
ENV[''RUBY_EXE''] gets set to :target by
mspec/lib/mspec/commands/mspec.rb, but it probably makes sense to move that into
mspec/lib/mspec/utils/script.rb so it gets called by all runners.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Thursday, February 26, 2009 12:35 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Yes, that would be a good idea; then .mspecrc or similar would have been loaded
before ruby_exe gets called.  I think they need to look at the implementation of
resolve_ruby_exe in that class anyway as I don''t think it looks at the
:target option but I might be wrong.  If that is true then you will still need
to set RUBY_EXE in the .mspecrc or similar file.
Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Jim Deville
Sent: Thursday,26 February 26, 2009 08:14
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

The other option, which I''ve already asked Brian Ford to do, is to not
find the force the RUBY_EXE evaluation unless the ruby_exe method is called.
That will make it only matter when you want to run a ruby_exe method. It sounds
like there might be another issue, but I''ll look into it.

JD

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 25, 2009 11:52 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK so I am running a recent (if not latest) pull from the github/rubyspec/mspec
repository.  May be that is the difference.  Neither .mspecrc or -B file get
loaded before the ruby_exe.rb so neither files will fix this problem.  The only
long term solution is to fix rbconfig.rb.  The short term one is to set RUBY_EXE
as an environment variable or as a ruby constant before any call to require
"mspec".
Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Thursday,26 February 26, 2009 07:09
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I am not sure how to describe our version of mspec. I don''t see any
version number in the mspec folder. Jim should confirm, but it must be the one
from http://github.com/ironruby/mspec/tree/master.

Btw, Jim is looking to make it easier to run mspec by adding a .mspecrc file and
some other utility commands. Lets see if that clears this up...

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Wednesday, February 25, 2009 8:31 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

Hi Shri,
I tried just using the -B option with this information inside my default.mspec
file but in my install of mspec, the default.mspec never gets loaded as the
ruby_exe.rb is required before the mspec.default file and it blows up inside
ruby_exe.rb.  The reason that mspec-debug.rb works is that the RUBY_EXE constant
is defined before mspec and therefore ruby_exe are required.
What version of mspec are you running?
Pete

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Shri Borde
Sent: Wednesday,25 February 25, 2009 21:33
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

I checked a bit, and I don''t have a RUBY_EXE environment variable, or a
%HOME%\.mspecrc file. Peter, did you use "-B /path/to/default.mspec"
in the ir.exe command-line, and does it set :target? I do have both of these,
and maybe that is why it works for me.

If mspec-debug.rb works for you, sure, you should add a note on the wiki about
it. I would be fine with using either a default.mspec (which already exists) or
a mspec-debug.rb.

Thanks,
Shri

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Pete Bacon Darwin
Sent: Tuesday, February 24, 2009 3:11 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Debugging rubyspecs

OK, this is what I mean.  I save the following file (attached also) as
Merlin/Main/Languages/Ruby/mspec-debug.rb:

RUBY_EXE =
''d:/dev/ruby/ironruby/current/Merlin/Main/Bin/debug/ir.exe''

$:.unshift ''d:/dev/ruby/mspec/lib''

require ''mspec/commands/mspec-run''
require ''mspec''

class MSpecScript
  set :target, RUBY_EXE
  set :flags, [ '' -D'']
  set :ci_files, ["rubyspec/1.8/core",]
  set :tags_patterns, [
    [%r(rubyspec/), ''ironruby-tags/''],
    [/_spec.rb$/, ''_tags.txt'']
  ]
end

MSpecRun.main

Once you have modified the paths for your setup, you can then run this file just
like mspec-run:

/path/to/ir.exe mspec-debug.rb /path/to/rubyspec/some_spec.rb

In the VS Ruby.Console project properties I set the following:

Start Action: Start Project
Start Options:
       Command Line Options: -D mspec-debug.rb -V
d:/dev/ruby/rubyspec/core/fixnum/abs_spec.rb
       Working Directory:
D:\dev\ruby\ironruby\current\Merlin\Main\Languages\Ruby\

Then I can set breakpoints in the C# code to debug and so on.

This solution is self contained, doesn''t require any environment
variables, doesn''t spawn any sub processes and doesn''t rely on
mspec guessing the ruby engine.  I personally don''t feel that it uses
too much of the internals of mspec: the configuration bits are public interfaces
to mspec and all we are doing is including a couple of files (that are unlikely
to change name) and running a single class method.

Let me know what you think.
Pete
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20090226/144ccb33/attachment-0001.html>

Ironruby core - Feb 2009 - Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs

[Ironruby-core] Debugging rubyspecs