[#RVM-357] Fatal error when synchronising on null objects

RVM

Created: 19/Dec/07 08:59 PM Updated: 20/Dec/07 10:18 AM

Component/s:

Compiler: Baseline

Affects Version/s:

2.9.2

Fix Version/s:

2.9.3

Time Tracking:

Not Specified

File Attachments:	1. SyncNull.java (0.2 kB)
Environment:	PPC OSX

Testcase included:

yes

Description

« Hide

The code for monitorenter does not always check that the argument is not null. This result in a NullPointerException inside uninterruptible code.

I have seen that on PPC OSX using the base compiler. I do not know whether this happens on other architectures/compilers.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

David Grove added a comment - 20/Dec/07 09:00 AM

Bug is confined to the baseline compilers, but is present on both IA32 and PPC.

Opt compiler generates correct code (does null check before entering uninterruptible locking region).

[ Permlink | « Hide ]

David Grove added a comment - 20/Dec/07 10:18 AM

fixed in r13920.