JDK-4934202 : JNIid need a proper support in SA code
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 5.0
  • Priority: P4
  • Status: Closed
  • Resolution: Not an Issue
  • OS: generic
  • CPU: generic
  • Submitted: 2003-10-08
  • Updated: 2019-08-15
  • Resolved: 2018-02-02
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.
JDK 11
11Resolved
Related Reports
Relates :  
JDK-8189798 - SA cleanup - part 1
Relates :  
JDK-4854296 - JNI ids must be reimplemented to support JVMTI obsolete ids, increase efficiency
Relates :  
JDK-7165259 - Remove BugSpot
Description
JNIid type has been removed in VM as part of 4854296 (reimplement jmethodID and jfieldID). SA's BugSpot code refers to this type. For now, relevant SA code has been commented out. Please sync. SA code with VM changes. 

###@###.### 2003-10-08
Comments
BugSpot was removed with JDK-7165259. And the JNIid.java file (since it did not have corresponding code in Hotspot) got removed in SA with JDK-8189798. I believe this can be closed.
13-11-2017
JNIid exists in hotspot workspace, but corresponding code is commented out in SA. This mess definitely need a cleanup.
07-08-2013
EVALUATION A class JNIid is defined in the Mustang and Dolphin workspaces: src/share/vm/oops/instanceKlass.hpp:class JNIid: public CHeapObj { Does that mean that this bug is now obsolete or just needs a different fix?
27-09-2006
EVALUATION This bug does not affect SA/JDI or any of the "unsupported" SA command line utils. This affects only "bugSpot" - liveprocess mixed mode debugger which is internally used. ###@###.### 2004-03-02
02-03-2004