| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2013825 | 1.1 | David Cox | P2 | Resolved | Fixed | 1.1beta3 |
While running the latest HotJava1.0 with the jvm11_04 build, with the JIT
enabled, a certain part of the browser's table processing code will
reliably produce a bogus nullPointerException. It occurs when the
following expression is encountered:
hasBorder = owner.needsBorder() && !isCaption;
one may play games with parens and with breaking the expression down into
separate statements, but the bug persists, until the following rewrite
is tried:
nb=owner.needsBorder();
tb=!isCaption;
hasBorder = nb && tb;
Everything then works "fine". Note: nb, tb, isCaption, and hasBorder are
all booleans.
enabled, a certain part of the browser's table processing code will
reliably produce a bogus nullPointerException. It occurs when the
following expression is encountered:
hasBorder = owner.needsBorder() && !isCaption;
one may play games with parens and with breaking the expression down into
separate statements, but the bug persists, until the following rewrite
is tried:
nb=owner.needsBorder();
tb=!isCaption;
hasBorder = nb && tb;
Everything then works "fine". Note: nb, tb, isCaption, and hasBorder are
all booleans.
- backported by
-
JDK-2013825 JIT may produce false nullPointerExceptions
-
- Resolved
-