JDK-4289109 : break points are not reported as expected
  • Type: Bug
  • Component: vm-legacy
  • Sub-Component: jvmdi
  • Affected Version: 1.3.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_7
  • CPU: sparc
  • Submitted: 1999-11-08
  • Updated: 2002-09-06
  • Resolved: 2002-09-06
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.3.0 kestrelFixed
Related Reports
Relates :  
Relates :  
Description
This happens in Hotspot Performance Engine in 1.3 fcs M build.

The number of Breakpoints hit is one more, than expected.

           for(int i=0; i<10; i++){
	        testMethod();
	    }
         .
         :
         :

	public static void testMethod(){
           System.out.println("I'm done");

	}
When break point is set in testMethod 
10 break points are supposed to be hit instead of 11.

This is reproducable using the debugger demo with the java file attached.
Compile with -g option.

jdb EventTest
stop in EventTest.testMethod()
run
cont
cont
:
till application ends.

10 Breakpoints are reported in Classic as expected.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: kestrel INTEGRATED IN: kestrel
14-06-2004

EVALUATION This was fixed as part of the fix for 4278333. There was a bug in stepping around breakpoints. I've verified that this bug no longer occurs. peter.kessler@Eng 1999-11-08
08-11-1999