JDK-4212394 : t104 in -Xcomp [NullPointerException must be thrown when synching on a null oop]
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 1.0
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_2.6
  • CPU: sparc
  • Submitted: 1999-02-17
  • Updated: 1999-06-22
  • Resolved: 1999-06-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.0 rc1Fixed
Related Reports
Relates :  
Description
Failure to throw NullPointerException in -Xcomp

class t104
{
    public static void main(String[] argv)
    {
	t104 o = null;
	try
	{
	    synchronized(o)
	    {
		System.out.println("Fubar: monitorenter didn't throw.");
	    }
	    System.out.println("Bottom of try block.");
	}
	catch(Throwable t)
	{
	    System.out.println("Exception thrown.");
	    System.out.println(t.toString());
	}
    }
}

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: 1.0_rc1 INTEGRATED IN: 1.0_rc1
14-06-2004

EVALUATION michael.paleczny@eng 1999-02-17 Compiler does not record that there is a NULL on the expression stack when constructing an uncommon_trap for a monitor_enter. Solution: Move the do_null_check out of do_lock and place it before popping the expression stack in do_monitor_enter
11-06-2004