- 
    Enhancement 
- 
    Resolution: Fixed
- 
     P3 P3
- 
    21
- 
        b11
                    It can be difficult to find the cause of calls to java.lang.System.exit(status) and Runtime.exit(status) because the Java runtime exits immediately.
Logging or printing a message and stack trace would make it easier to locate the caller and cause.
Logging or printing a message and stack trace would make it easier to locate the caller and cause.
- csr for
- 
                    JDK-8302691 System.exit and Runtime.exit debug logging -           
- Closed
 
-         
- relates to
- 
                    JDK-8303198 System and Runtime.exit() resilience to logging errors -           
- Resolved
 
-         
- 
                    JDK-8367597 Runtime.exit logging failed: Cannot invoke "java.lang.Module.getClassLoader()" because "m" is null -           
- Resolved
 
-         
- 
                    JDK-8303057 vmTestbase/nsk/jdi/VMOutOfMemoryException/VMOutOfMemoryException001/VMOutOfMemoryException001.java fails -           
- Closed
 
-         
             (1 links to)
        
     
        