At 01:33 PM 4/6/00 -0500, you wrote:
>I'm using JDEbug in 2.1.6 beta 22 and am wondering if there is a way to
>inspect variables other than local ones (i.e., class variables). If I'm
>debugging a class that declares
>
> private static String configDir = null;
>
>and have the point in configDir in the statement
>
> if (configDir != null) {
>
>and do JDEbug->Display->Variable, I get the message:
>
>Error: cannot evaluate "configDir".
> Reason: Parse error in expression. Are you accessing local variables
>without compiling with -g?.
>
>I can point at variables local to the function and it works
>properly. Typing in "this.configDir" and trying to display that doesn't
>work either.
>
Hi Steve,
This ia a serious hole in the present implementation. I did some
investigation into the JPDA spec and it turns out that it is possible for
the JPDA to get the "this" object for each stack frame. Consequently, I
will update the local variables buffer so that it always shows the "this"
object for the current stack frame. Given the local variables and the this
object, you should be able to inspect every object accessible at the
current point in the program. I'll include this change in the next release
which I plan to make over the weekend.
- Paul
------------------------------------------------------------
TECH SUPPORT POLICY
I respond only to requests that contain a complete problem report. The
easiest way to ensure that your report is complete is to include the output
of the JDE->Help->Submit Problem Report command in your request.
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JDE website: http://sunsite.auc.dk/jde/
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
