-
Bug
-
Resolution: Fixed
-
P2
-
5.0, 5.0u1
I believe this started with b26 and is caused by the fix for 4870514.
A testcase is in
/net/jano.sfbay/export/disk20/serviceability/ws/regressionTestsInWaiting/LineNumberOnBraceTest.java
In this construct:
if (...) {
stmt1
} else {
stmt2
}
stmt3
If a debugger user is stopped on stmt1 and does a 'next',
the debugger should stop at stmt3. This bug causes it
to stop instead on the } else { line. This forces the user
to do a second 'next' to get to the stmt3 line.
###@###.### 10/5/04 00:35 GMT
A testcase is in
/net/jano.sfbay/export/disk20/serviceability/ws/regressionTestsInWaiting/LineNumberOnBraceTest.java
In this construct:
if (...) {
stmt1
} else {
stmt2
}
stmt3
If a debugger user is stopped on stmt1 and does a 'next',
the debugger should stop at stmt3. This bug causes it
to stop instead on the } else { line. This forces the user
to do a second 'next' to get to the stmt3 line.
###@###.### 10/5/04 00:35 GMT
- duplicates
-
JDK-6359542 Debugger always stepping through if and else statement blocks
- Closed
- relates to
-
JDK-4870514 Bad mapping between bytecode and line number.
- Resolved
-
JDK-4482888 javac produces unverifiable classfile compiling conditional operator
- Resolved