P2
This "jdb craches JVM" bug is reported by our ISV, NetDynamics, Inc.
It only happen under NT (no test have done under Solaris yet)
To reproduce the problem for JDK 1.1, just write a simple application that
display a frame when a button was hit. Place a breakpoint (with jdb) on the
event handler (1.0.2 event style) for the button and the JVM that was running
the application crashed with an access violation. (see the attachement for
the test case)
Some background here:
NetDynamics is trying to use the sun.tools.debug package to interface with the JDK debugger. They are writing a GUI debugger using this interface to debug Java
applications. They claims interface works fine, it seems the bugs lie in the JVM itself. Under JDK 1.1 the debugger doesn't work at all. They have mentioned some bugs they found in JDK 1.02:
- No support for local variables that aren't scalar or array's
- No support for stepping out (i.e. run until the current function exits)
- Crashes in the JVM when stepping out of scope of a function
Since the 1.1 debugger crashes at such an early stage, they can't confirm if
above bugs are still existing at JDK1.1.
Dave Brewster suggested that if we could get them a quick patch for the jdb 1.1
bug, then they can test the rest. Feel free to call Dave if you need any other
info -- 415.462.7633
It only happen under NT (no test have done under Solaris yet)
To reproduce the problem for JDK 1.1, just write a simple application that
display a frame when a button was hit. Place a breakpoint (with jdb) on the
event handler (1.0.2 event style) for the button and the JVM that was running
the application crashed with an access violation. (see the attachement for
the test case)
Some background here:
NetDynamics is trying to use the sun.tools.debug package to interface with the JDK debugger. They are writing a GUI debugger using this interface to debug Java
applications. They claims interface works fine, it seems the bugs lie in the JVM itself. Under JDK 1.1 the debugger doesn't work at all. They have mentioned some bugs they found in JDK 1.02:
- No support for local variables that aren't scalar or array's
- No support for stepping out (i.e. run until the current function exits)
- Crashes in the JVM when stepping out of scope of a function
Since the 1.1 debugger crashes at such an early stage, they can't confirm if
above bugs are still existing at JDK1.1.
Dave Brewster suggested that if we could get them a quick patch for the jdb 1.1
bug, then they can test the rest. Feel free to call Dave if you need any other
info -- 415.462.7633