Created by Wang, Jerry on Jan 09, 2017
http://stackoverflow.com/questions/33053153/eclipse-luna-cannot-watch-variables-in-hashmap-errors-during-the-evaluationThe reason beyond that is that the bytecode (.class files) used by your Eclipse debugger doesn’t contain any information about method parameters name. That’s the way the JDK is compiled by default.
The Eclipse debugger implements a workaround for method parameters, naming them “arg0”, “arg1”, etc. and thus enabling you to inspect them in the “Variables” view. Unfortunately, I don’t think there is such a workaround for local method variables…
Some other tickets in StackOverflow advise to rebuild yourself the JRE based on source code of the JDK, e.g.: debugging not able to inspect the variables.
