Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 4424381
Votes 0
Synopsis TEST_BUG: Some tests use null-statement badly
Category hotspot:test
Reported Against merlin
Release Fixed ladybird, 1.4(merlin) (Bug ID:2113100)
State 11-Closed, Verified, bug
Priority: 3-Medium
Related Bugs 4083890
Submit Date 12-MAR-2001
Description





The following tests have unreachable statements, so they fail to compile.

    nsk/coverage/classFileParser/classFileParser002
    nsk/coverage/classLoader/classLoader001
    nsk/coverage/classLoader/classLoader002
    nsk/coverage/classLoader/classLoader003        
    nsk/logging/LogManager/setLevel/setlevel002
    nsk/stress/numeric/numeric002
    nsk/stress/stack/stack016

A semicolon in a method body is a null statement. The tests use 
null statement after return statement in method, so  customer  `;` 
is unreachable.    

The following method is not compiled because the second semicolon is 
a different statement and is unreachable:

    public static int run(String argv[], PrintStream out) {
        return 2 /*STATUS_FAILED*/;;
    }

Since jdk1.4.0-beta-b53 the compiler detects unreachable empty 
statements as required by the language specification.
See bug:

    4083890: Empty statements are not marked as unreachable
    
======================================================================
Work Around
N/A
Evaluation





I removed unreachable null-statments from the tests.
Fixed in testbase_nsk.v14r02

Alexey Gibadullin,   xxxxx@xxxxx           Date: 03/15/2001


======================================================================
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang