Charles,
I tried out the patch, but there is a small bug: the expression
implementationClass.getBaseName() sometimes return null, thus causing a NPE
when constructing a StackTraceElement.
I am a little confused about the purpose of the patch though. Is it
suppose to handle internal JRuby exceptions, such as NPE or CCE? I applied it
and it runs fine, but a NPE from AR-JDBC's internal adapter still shows through
with no Ruby source file information on the trace.
Peter
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charles Oliver
Nutter
Sent: Wednesday, April 23, 2008 12:49 PM
To: [email protected]
Subject: [jruby-dev] Including interpreted Ruby frames in Java stack trace
Attached is a patch that makes it possible to include interpreted Ruby method
information in the Java stack trace of a raised exception. This mechanism would
help users of Ruby from Java produce a stack trace that shows exactly where an
error happened, including both Ruby and Java stack trace information. But it's
a little hacky at the moment. If anyone wants to play with it and clean it up,
making sure it doesn't break anything, I'd appreciate it. It was my 30-minute
experiment for the day.
Here's what the trace looks like: http://pastie.org/185586
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
