|
Quick Lists
|
|
Bug ID:
|
6432085
|
|
Votes
|
0
|
|
Synopsis
|
Stack Trace does not show up on NullPointerException in 1.4.2 (-server VM)
|
|
Category
|
hotspot:runtime_system
|
|
Reported Against
|
|
|
Release Fixed
|
|
|
State
|
11-Closed, duplicate of 4292742,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
4292742
|
|
Submit Date
|
31-MAY-2006
|
|
Description
|
Stack Trace does not appear on NPE in 1.4.2_11.
Configuration :
UltraSparcII 400[MHz] *2
4[GB]
Solaris9
How to reproduce :
1. Compile attached .java programs
2. Launch
" java -server -cp . TestNPO 100"
in 1.4.2_11 on Solaris9 box.
The following message will show up.
...
Thread-72 start
Thread-83 start
Thread-54 start
Thread-52 start
Thread-81 start
Thread-88 start
Thread-58 start
java.lang.NullPointerException
java.lang.NullPointerException
java.lang.NullPointerException
java.lang.NullPointerException
Although NPE occurs several times, stack trace does not show up.
Posted Date : 2006-05-31 08:37:04.0
|
|
Work Around
|
Use -XX:-OmitStackTraceInFastThrow.
|
|
Evaluation
|
It's quite possible the missing stack trace is due to 6428459 which appears to be a c2 issue. We'll re-evaluated this after 6428459 is fixed.
Posted Date : 2006-06-07 14:10:09.0
It turns out this is unrelated to 6428459, in fact it appears to be a duplicate of 4292742. The spec does not dictate that stack traces must appear for all exceptions. Current behavior, c2 will include the stack trace; after recomplication, it may revert to the older, faster mechanism and omit a trace. -XX:-OmitStackTraceInFastThrow may be used to force stack trace always, at the cost of performance.
Posted Date : 2006-06-30 13:20:17.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |