Examine @CS methods when called from attached thread with no caller

XMLWordPrintable

      Reflection::getCallerClass may return null if there is no caller on the stack. We need to examine @CS methods when called from a thread attached via JNI for proper handling of the null caller class case. We should create new tests to catch these cases.

        1.
        		 MethodHandles::lookup throws NPE if caller is null Sub-task Resolved Tim Prinzing (Inactive)  
        2.
        		 ClassLoader::registerAsParallelCapable throws NPE if caller is null Sub-task Resolved Tim Prinzing (Inactive)  
        3.
        		 Class::forName(String) defaults to system class loader if the caller is null Sub-task Resolved Tim Prinzing (Inactive)  
        4.
        		 System::setSecurityManager may throw NPE if the caller is null Sub-task Closed Mandy Chung (Inactive)  
        5.
        		 Module::getResourceAsStream should check if the resource is open unconditionally when caller is null Sub-task Resolved Tim Prinzing (Inactive)  
        6.
        		 java.io.ObjectStreamClass::forClass and java.io.ObjectStreamField::getType throw NPE when caller is null Sub-task Closed Mandy Chung (Inactive)  
        7.
        		 javax.sql.rowset.serial.SerialJavaObject::getFields may throw NPE if caller is null Sub-task Closed Mandy Chung (Inactive)  
        8.
        		 ResourceBundle::getBundle may throw NPE when invoked by JNI code with no caller frame Sub-task Resolved Tim Prinzing (Inactive)  

            Assignee:
            Mandy Chung (Inactive)
            Reporter:
            Mandy Chung (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: