JDK-4303298 : Duplicate breakpoint reporting in JVMDI causes wrong JDI counted bp behavior
  • Type: Bug
  • Component: vm-legacy
  • Sub-Component: jvmdi
  • Affected Version: 1.3.0
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_7
  • CPU: sparc
  • Submitted: 2000-01-07
  • Updated: 2000-05-18
  • Resolved: 2000-05-18
Related Reports
Duplicate :  
Relates :  
Description
BreakpointRequest.addCountFilter(int) should report one event only when 
 the count reaches 0.
 The event should be reported when the value of field "i" in class Test1 is 
 5 that is when the filter count reaches zero. The testcase behaves as 
 expected in Win32 Classic, Win32 Hotspot and Solaris Classic.
 In **Solaris Hotspot** the event is reported(at "i=2") even before 
 the filter count reaches zero.

 Testing done in JDK1.3.0-R build.

 Steps to reproduce the bug
 ---------------------------
 1)Set path to latest JDK
 2)Compile the attached files with -g option
 3)Start the targetVM with the command
 java -Xdebug -Xnoagent 
 -Xrunjdwp:transport="dt_socket",server=y,suspend=y,address=5670 Test1
 4)Start the debugger with the command
 java CountBugTest

 Attachments:
 ------------
 1. JDIScaffold.java
 2. VMConnection.java
 3. CountBugTest.java
 4. Test1.java

Comments
EVALUATION gordon.hirsch@eng 2000-01-26 It appears that the hotspot (solaris only) vm is reporting duplicate breakpoints. This can be seen pretty easily if the following line is removed from CountBugTest.java. request.addCountFilter(5); I'm reclassifying this as a hotspot/jvmdi bug. daniel.daugherty@Eng 2000-05-18 This bug is not reproducible using solaris_baseline (Beta1) on SPARC nor on Win32 (expected). I found a relevant fix that was integrated for Kestrel Solaris production and not for Kestrel Solaris reference (Kestrel FCS-C): 4294585 4/5 HotSpot 1.3fcs-P generates unexpected JVMDI_EVENT_BREAKPOINT events on Solaris I am closing this bug as a duplicate of 4294585.
11-06-2004