JDK-4506433 : Tools vendors: debugging is too slow
  • Type: Bug
  • Component: vm-legacy
  • Sub-Component: jvmdi
  • Affected Version: 1.4.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2001-09-24
  • Updated: 2002-08-30
  • Resolved: 2002-08-30
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
1.4.0 beta3Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Description
Borland, Metrowerks, the Forte tools group, and other vendors have pointed out
that debugging via JVMDI, and thereby enabling interpreted-only mode, has too
much of a performance hit to be effective when debugging large applications.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin-beta3 FIXED IN: merlin-beta3 INTEGRATED IN: merlin-beta3 VERIFIED IN: merlin-beta3
14-06-2004

EVALUATION ###@###.###, ###@###.###, and I have implemented full- speed debugging in JVMDI to address this performance issue. ###@###.### 2001-09-24 After consultation with Borland, full-speed debugging has been made the default for 1.4 Beta 3. ###@###.### 2001-09-25 ============================================================================= ###@###.### 2002-01-04 Full speed debugging feature is being implemented and integrated into merlin build. Updating this bug as fixed. If anybody else has different opinion, can remove the verification marked, and explain what they want more.
11-06-2004