JDK-5026971 : (hotspot) Clean up hiding of exception backtrace field
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.5.1
  • Priority: P5
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2004-04-05
  • Updated: 2014-02-06
  • Resolved: 2012-09-20
Related Reports
Relates :  
JDK-6978918 - Should clear stackTrace before throwing the preallocated default OutOfMemoryError objects
Relates :  
JDK-5012949 - Reflect.Instances.add of a null causes a Sig 11 in 1.4.2
Relates :  
JDK-8033735 - make Throwable.backtrace visible to Class.getDeclaredField again
Relates :  
JDK-5026972 - (classes_lang) Clean up hiding of exception backtrace field
Relates :  
JDK-4496456 - Segmentation fault introspecting ((Throwable) obj).backtrace[0][0]
Description
4496456 illustrated the need to hide the "backtrace" field in
java.lang.Throwable from consumption by reflection. 5012949 illustrated the need
to hide some additional fields in other classes. The mechanism introduced in the
Java libraries for 5012949 is more general than the code added to jvm.cpp for
4496456; we should remove the code in the VM for 4496456 and filter out the
backtrace field at the Java level.
Comments
EVALUATION Upon further thought it is not clear that the mechanism added in 5012949 is sufficient for all situations where fields need to be hidden, in particular JVMTI (where we must hide this field from the debugger and where it is queried via another mechanism than reflection).
19-12-2005
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: dragon
14-06-2004
EVALUATION Minor cleanup but should be done for 1.5.1. ###@###.### 2004-04-05
05-04-2004