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.
Tomas
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Letterle
Sent: Tuesday, September 23, 2008 5:47 AM
To: [email protected]
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 <[EMAIL PROTECTED]<mailto:[EMAIL
PROTECTED]>> 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
files.
Thanks
Jay Turpin
--
Posted via http://www.ruby-forum.com/.
_______________________________________________
Ironruby-core mailing list
[email protected]<mailto:[email protected]>
http://rubyforge.org/mailman/listinfo/ironruby-core
--
Michael Letterle
[Polymath Prokrammer]
http://blog.prokrams.com
_______________________________________________
Ironruby-core mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-core
