In the debug interpreters, we seem to be having trouble
accessing some private/protected fields and methods
which should be in scope. It's still unclear exactly
which cases work and which don't, but we should make an
effort to provide access to anything that would
normally be accessible in the method itself.
In the short term, we can simply react if we are denied
access to *any* field/method in a debug interpreter,
granting access to it by circumventing the
accessibility system with reflection. (This is done
with a technique shown in the PrivilegedAccessor class:
http://groups.yahoo.com/group/junit/files/src/PrivilegedAccessor.java\)
In the long term, we should be more accurate and
prevent access to private fields and methods that the
user actually shouldn't have access to.