RFA: JVMTI GetFrameCount

Tom Tromey tromey@redhat.com
Mon Jul 31 20:29:00 GMT 2006


>>>>> "Kyle" == Kyle Galloway <kgallowa@redhat.com> writes:

Kyle> This implies that we need to suspend the thread, at least temporarily, 
Kyle> to keep the interpreter from crashing.  The problem being that JVMTI 
Kyle> doesn't use a suspend count for each thread.

Another solution is to keep a flag indicating whether the thread is
currently suspended.  That should be sufficient in this case.
But ... whatever you and Keith think is best.

Kyle> This is more a problem with the structure of the stack from within the 
Kyle> interpreter.  The structure that the thread is aware of is a linked list 
Kyle> containing only the interpreted stack frames.  The easiest way to fix 
Kyle> this would simply be to create a superclass to hold either the current 
Kyle> _Jv_InterpFrame structure or a placeholder for a native call so that the 
Kyle> JVMTI functions will be aware of it.  Is there another way to do this?

Yeah, we have a bunch of stack-tracing machinery.  See stacktrace.cc.
Offhand I don't recall whether this works on an arbitrary thread or
only the current thread -- but presumably it could be generalized if not.

Tom



More information about the Java-patches mailing list