> While debugging, How would you make sure that you can view the local
> ('auto' qualified) variables in your debugger's variable window?
[quoted text clipped - 14 lines]
> variable window there is a message that states "local variables
> unavailable" next to the current stack for the thread you are on.
Sounds like you are compiling without the debug information.
If you are compiling using javac then add a -g flag.
If you are compiling using ant then add debug="true" as an attribute to
your javac task call.
If you are using eclipse to compile then you are on your own. I avoid
Eclipse like the plague.
TrevorBoydSmith@gmail.com - 12 Dec 2006 18:38 GMT
Wesley,
Your instinct was correct. The correct debugging flags were not in
place. So when I did my debugging it did not have the debugging info
it needed to show the 'local variables' values.
The way I fixed it was to reset Eclipse. Then when I ran debugging
again I could see all the local variables without a hitch.
For those of you interested in wondering how Eclipse handles debugging
I did some research before I thought about just resetting Eclipse to
fix it:
-when you do the common 'run java application' it compiles the program
with default settings for running a java application
-when you do the common 'debug java application' it compiles
differently and hands you off to the debugging tools associated with
the Eclipse Java Dev Tools.
-Probably, when i did 'debug java application' the settings did not
switch and so the eclipse debugging tools did not get all the symbolic
debugging info that was needed.
-Trevor
> > While debugging, How would you make sure that you can view the local
> > ('auto' qualified) variables in your debugger's variable window?
[quoted text clipped - 24 lines]
> If you are using eclipse to compile then you are on your own. I avoid
> Eclipse like the plague.