Re: [jdt-debug-dev] Issue relating to wrappering jdt debug model

["Darin Wright" <Darin_Wright@xxxxxxx>]

If you must "step and check" then there is not much you can do to improve performance. If you know where you want to end up, setting an "invisible" breakpoint would be more efficient.

Darin

David Sanders <dsanders@xxxxxxxxxxx> Sent by: jdt-debug-dev-admin@xxxxxxxxxxx 10/10/2002 05:11 PM Please respond to jdt-debug-dev

To:        jdt-debug-dev@xxxxxxxxxxx         cc:                 Subject:        [jdt-debug-dev] Issue relating to wrappering jdt debug model

Hello,

We are having some performance issues with our step into functionality
of our wrapper for JDIThread.  The problem is that for every "step
into" of one of our statements, we require several "step into" calls
in the underlying JDIThread.  After each of these JDIThread step into
calls, we must get the top stack frame and check to see if we should
continue stepping into the JDIThread.  The problem is that each of our
getTopStackFrame calls results in a call to 
org.eclipse.jdi.internal.ThreadReferenceImpl's frames(int,int) method, 
which can result in a significant time penalty when having to do this
many 
times.  Any suggestions?

Regards,

David
_______________________________________________
jdt-debug-dev mailing list
jdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-debug-dev