| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2056504 | 1.4.2 | Tom Rodriguez | P4 | Resolved | Fixed | mantis |
| JDK-2056503 | 1.4.1_02 | Tom Rodriguez | P4 | Resolved | Fixed | 02 |
A licensee (see comments for details) has isolated a bug in the null-check
eliminator. Since exception handlers are not traversed during the dataflow
walk, incorrect not-null results can be created for values which are assigned
null values inside of exception handlers. This may cause a VM crash if such
compiled code is ever executed and if the receiver is dereferenced at a point
where the compiler assumed the receiver was non-null. A patch has been
submitted.
eliminator. Since exception handlers are not traversed during the dataflow
walk, incorrect not-null results can be created for values which are assigned
null values inside of exception handlers. This may cause a VM crash if such
compiled code is ever executed and if the receiver is dereferenced at a point
where the compiler assumed the receiver was non-null. A patch has been
submitted.
- backported by
-
JDK-2056503 Null-check eliminator must traverse exception handlers
-
- Resolved
-
-
-
- Resolved
-
- duplicates
-
JDK-4759909 jdk 1.4.0 client VM crashes
-
- Closed
-