VM 1.4.0-beta_refresh-b72

Steps to reproduce:
Use jdb to debug the folloving class:

public class Test {
    public static void main (String [] args) {
        String s = new String ("");
        System.out.println ("the end");
    }
}

- start jdb
- set breakpoint at Test:3 (line containing String s = new String ("");
- run Test, jdb stops at line 3
- try trace over (next), jdb does not stop at line 4, the whole main method is executed

It seems that resume insted of trace over occurs if a line containg a method call is executed.

This buggy behaviour of Trace over can be reproduced using Forte4j's debugger as well.


ingrid.yao@Eng 2001-07-31

Same bug reported by CAP member:
---------------------------------
J2SE Version (please include all output from java -version flag):
  Java(TM) 2 Runtime Environment, Standard Edition (build
  1.4.0-beta_refresh-b72)

  Java Debug Wire Protocol (Reference Implementation) version 1.4
  JVM Debug Interface version 1.2
  JVM version 1.4.0-beta_refresh (Java HotSpot(TM) Client VM, interpreted
      mode)

Does this problem occur on J2SE 1.3?
  No

Operating System Configuration Information (be specific):
  Windows 2000, Service Pack 1

Hardware Configuration Information (be specific):
  Intel Pentum III, 1ghz, 512mb

Bug Description:
  inconsistent stepping behavior (JPDA);
  "stepping over" function calls does not halt execution at line of code
  following a function call.
  stepping over statements other than function calls does work as expected.
  "stepping out" does not halt execution at calling stack frame at line of
  code following the function call.
  "stepping into" works as expected.

  problem seems to be on the debuggee (target vm) side (JVMDI?), as this bug
  can be reproduced with JDI-based debuggers (such as jBuilder) and
  JDWP-based products.

Steps to Reproduce (be specific):
  bug can be reproduced with any JPDA-based debugger (such as jBuilder) by
  stepping through code with function calls.