JDK-4920005 : jang.lang.instrument (JPLIS) methods don't check for null
  • Type: Bug
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 5.0
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2003-09-10
  • Updated: 2003-09-26
  • Resolved: 2003-09-26
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 tigerFixed
Related Reports
Relates :  
JDK-4882798 - JPLIS: Java programming language agents need instrumentation support (JSR-163)
Description
JCK development at Altaworks has encountered a consistent crash in their
tests.  It has been tracked to JPLIS native support passing NULL to a
JNI function which crashes (JNI does not check incoming parameters).
The crashing method is Instrumentation.appendToBootstrapClassLoaderSearch.
But more broadly, there are several null checks missing from the JPLIS
interface.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b22
14-06-2004
EVALUATION Must be fixed ASAP.
11-06-2004
SUGGESTED FIX Jeff has pointed out that this checks should occur at the Java programming language level.
11-06-2004
PUBLIC COMMENTS jang.lang.instrument functions don't check for null - some crash
10-06-2004