Tested Platform: Solaris 10-sparc (32 & 64 bits) (using JDS as windows manager)
                  Windows XP-Home(sp2), Windows 2003
                  
Tested JRE: Mustang-b59b

Failing Tests: CTE_REGTEST/Generic/4486859 (Sustaining manual regression test case)


When we execute command "Print e" at main [1] prompt, below exeception was displayed saying, "com.sun.tools.example.debug.expr.ParseException: Name unknown: e e = null "
It ended up with "Fatal error: Failed reading output of child java interpreter"

It appears a regression. We noticed the same test passed on solaris 10 sparc -64 bit
(in b57)and XP-Home (in b58) (no exception thrown)

Testcase and instruction are available at :
========================================
/net/jdk/export/jpse04/Regression/1.6.0/test/CTE_REGTEST/Generic/4486859

Steps to reproduce:
==================
1. Complie the java file with -g option:
    javac -g JavacTest.java

2. Start the test using jdb:
    jdb JavacTest

3. Issue 'stop at JavacTest:7' and then 'run' commands at jdb prompt.

4. When the break point is hit, issue 'print e' command.

The "com.sun.tools.example.debug.expr.ParseException" shouldn't occur but it does.
The test instruction needs to be modified to avoid the ambiguity/anomaly.

Current test procedure is ambiguous to the "Check" point of the test case.

*****************************************************************************
Check point is:
---------------
 If the debugger crashes and you see the following error - test FAILED
       'HotSpot Virtual Machine Error'
 and 'The application has been disconnected'
 
 If the program does not crash - test PASSED
     in 'main[1] prompt type 'exit' and hit 'Return/Enter' key to stop
*********************************************************************************

The result is that the program does not crash and there is no "HotSpot Virtual Machine Error" error.

BUT the procedure does not ask to check "com.sun.tools.example.debug.expr.ParseException: Name unknown: e
      e = null " exception when executing command "Print e" at main [1] prompt.

hence, the test still reported as PASSED.

This behaviour occurs in all version of JREs.