Other | Other |
---|---|
1.3.0Fixed | 1.3.1 1.3.1Fixed |
Duplicate :
|
|
Duplicate :
|
|
Relates :
|
|
Relates :
|
|
Relates :
|
|
Relates :
|
|
Relates :
|
|
Relates :
|
|
Relates :
|
Several bugs describe the behavior of stopping twice at a breakpoint: 4278333 & 4331369 & 4326260 & 4294585 & 4303298 This may just be another dup but I am submitting it because it has the additional property of crashing the VM. Test program: ---- cut here --- public class BPTest { public static void main(String[] args) { for(int i=0; i < 100; i++){ System.out.println("i = " + i); BPTest Instance = new BPTest(); // add breakpoint here !! } } } ---- cut here --- The run (on Merlin/Solaris): % jdb BPTest Initializing jdb... > stop at BPTest:5 Deferring breakpoint BPTest:5. It will be set after the class is loaded. > run run BPTest Java HotSpot(TM) Client VM warning: Setting of property "java.compiler" is ignored > VM Started: Set deferred breakpoint BPTest:5 i = 0 Breakpoint hit: thread="main", BPTest.main(), line=5, bci=30 5 ErrorTest Instance = new ErrorTest(); // add breakpoint here !! main[1] resume All threads resumed. > Breakpoint hit: thread="main", BPTest.main(), line=5, bci=30 5 ErrorTest Instance = new ErrorTest(); // add breakpoint here !! main[1] resume All threads resumed. > # # HotSpot Virtual Machine Error, Unexpected Signal 11 # # Error ID: 4F533F534F4C415249530E43505007CA 01 # The application has been disconnected %
|