Description Jared Burns 2002-07-08 10:27:40 EDT

This problem was exposed by Bug 12966, which deals with debugging Sun's 
J2ME WTK. The debug proxy for this toolkit is a bit flaky, which in turn 
exposed this weakness in our code.

JDIModelPresentation.getText catches DebugException and returns "<not 
responding>". The methods that it delegates to just throw DebugException. 
The end result is that if we get an exception when asking about any single 
piece of data for a stack frame, we don't give the user any information. We 
can do better.

I've fixed JDIModelPresentation.getStackFrameText() and getVariableText() 
to wrapper each query (declaring type, receiving type, method name, line 
number, etc.) in a try/catch. This way, we can just say "<unknown x>" if an 
exception occurs retrieving any information x.

This is a big win. Instead of seeing "<not responding>" on the stack frame,
I now get 
"com.sun.kvem.midp.lcdui.EmulEventHandler$EventLoop(java.lang.Object).getClass()<unknown
line number>"