RVM

Fatal error when synchronising on null objects

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.9.2
  • Fix Version/s: 2.9.3
  • Component/s: Compiler: Baseline
  • Labels:
    None
  • Environment:
    PPC OSX
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
David Grove added a comment -

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).

Show
David Grove added a comment - 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).
Hide
Permalink
David Grove added a comment -

fixed in r13920.

Show
David Grove added a comment - fixed in r13920.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.