From Charile
Any thoughts on this? Does anyone else have need for lighter-weight
name/file/line inspection of the call stack?
Yeah I need it for my debugger and error displays. But I need it for
suspended threads
( my debugging steps ) as well as for exceptions. And for exceptions it
would
On 07/08/2012 12:03 AM, Charles Oliver Nutter wrote:
Today I have a new conundrum for you all: I need stack trace
generation on Hotspot to be considerably faster than it is now.
In order to simulate many Ruby features, JRuby (over)uses Java stack
traces. We recently (JRuby 1.6, about a year
On Saturday, July 7, 2012, Rémi Forax wrote:
You can use Throwable.**getStackTraceElement()
which is package visible and OpenJDK specific but at least
it will be faster for all VMs that uses OpenJDK.
I'll certainly explore that to see if it improves the situation. If it's
faster, it might be
On 07/08/2012 12:50 AM, Charles Oliver Nutter wrote:
On Saturday, July 7, 2012, Rémi Forax wrote:
You can use Throwable.getStackTraceElement()
which is package visible and OpenJDK specific but at least
it will be faster for all VMs that uses OpenJDK.
I'll certainly explore that
