[Ironruby-core] question on RubyGems

Tomas Matousek Tomas.Matousek at microsoft.com
Tue Sep 23 12:16:37 EDT 2008

You can also use tracing proc:

Hook it in a code:
set_trace_func proc { |*a|
  p a

and run ir.exe with -trace option.

Note that stack traces are not available in -X:Interpret mode yet and in compiled mode they contain some internal frames. It's the next item in my TODO list to fix that.


From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Michael Letterle
Sent: Tuesday, September 23, 2008 5:47 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] question on RubyGems

-D should give you script line numbers on the stack trace.
On Tue, Sep 23, 2008 at 8:42 AM, Jay Turpin <lists at ruby-forum.com<mailto:lists at ruby-forum.com>> wrote:
I did some research into getting rubygems and rake to work in IronRuby.
The first thing I had to do was set the ENV variable GEM_PATH to the
IronRuby/lib/ruby/gems/1.8 directory. That enabled rubygems to at least
locate the rake gem.

But now I'm stuck on an possible issue in the rubygems library. Looks
like it is handling the version numbers of the libraries differently
than Ruby. I'm looking into it further.

Does anybody know how to do a --trace to print out the script callstack?
It would certainly make it easier to track down problems in the .rb

Jay Turpin
Posted via http://www.ruby-forum.com/.
Ironruby-core mailing list
Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org>

Michael Letterle
[Polymath Prokrammer]

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

More information about the Ironruby-core mailing list