Name: md23716 Date: 01/10/2000


An internal customer of ours is having a problem using RemoteDebugger, due to the fact that the sourcepath setting is different in 1.2.2 to that in 1.1.7.

Email from us to our customer.....
For 1.1.7, the debug agent automatically picks up the system property
'java.class.path' as the source file path it uses.
For 1.2.2, this doesn't happen - it defaults to the current directory
only. With JDB you can use -Denv.class.path=
to force a classpath for the debug agent. You could use RemoteDebugger.setSourcePath() to apply the
debugger's classpath to the debuggee - is this a viable workaround
for you ?

Response from our customer.....
Thanks for the information. Yes if you pass the "class.path" property
to jdb it can find the source. However, as you mentioned that does not
help us for our debugger. We definitely need to have this problem
fixed, but I can provide a workaround in the debug engine which would
be adding the "class.path" property to the source search path. I
rather not modify the RemoteDebugger source path look up by using
setSoucePath() because it contradicts the use of that class to find
the source path in the first place. The call to
RemoteDebugger.getSourcePath() should return the correct
source path in 1.2.2 as it did in 1.1.7 . The workaround will only be
a temporary solution until we get a fix.

Reason for raising SunBug:
We want our product to remain in line with Sun, and will adopt whatever change Sun implements, to preserve the priciple of WORA.
This looks like a deliberate change in 1.2.2, but it is not backwards compatible and is causing a problem. This should be justification for a fix.
(Review ID: 99784)

======================================================================