At 05:07 PM 7/13/00 -0700, you wrote:
>Hello Paul-
>This may be a setup problem, but I cant figure it out. JDEbug can find
>the source for the file where the main method is, so I can see all the
>variables. But when I try to step into source code corresponding to
>another file I get the error below:
>
>------------------
>Resolved breakpoint set in ModelGenerator.java at line 89.
>Breakpoint hit at line 89 in com.eride.model.ModelGenerator
>(ModelGenerator.java) on thread main. All threads suspended.
>Error: cannot get local variables.
> Reason: Local variable information not available: compile with -g.
>Stepped to line 243 in java.lang.ClassLoader (ClassLoader.java) on
>thread main. All threads suspended.
>------------------
>
>This is in spite of compiling all the files (including the one where
>main is) with -g
>
>Why would it have variable information only for the main source file
>from which I start the debugger ?
>

Hi George,

I believe the error is occuring when you issue a step command that takes
you to a line that requires a class to be loaded. The next line therefore
is in the JDK class ClassLoader, which is compiled with no debug
information. I plan to add a capability to the debugger such that it will
by default skip step commands into basic classes like ClassLoader. You will
also be able to specify other classes or packages to skip. I will get to
this ASAP but it may be a while because I am busy fixing other problems at
the moment. In the meantime, you should be able to ignore these errors and
continue debugging.

Regards,

- 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



Reply via email to