-
Bug
-
Resolution: Cannot Reproduce
-
P2
-
None
-
1.4.2
-
x86
-
windows_2000
-----------------------------------------------------------------------------
Tests failed : nsk/jdb/regression/b4689395
Testbase : testbase_nsk
VM failed : server/client
Mode : -Xcomp/-Xmixed
JDK failed : 1.4.2-b18
platforms : WIN/solsparc
-----------------------------------------------------------------------------
This test passed in mantis beta b17
=====================================================
Regression test for the bug
4689395 (P4/S3) "step over" after a class is redefined acts like "step out"
Release summary: 1.4
Hardware version: generic
O/S version (unbundled products): 5.8
The test consists of two java-files:
b4689395.java - launches jdb and debuggee, writes commands to jdb,
reads the jdb output;
b4689395a.java - the debugged application.
The debugged application (b4689395a.java) defines method minor() that
prints four lines into System.out. b4689395 sets a breakpoint on the 31st
line
System.out.println("A breakpoint is here.");
and then redefines b4689395a with newclass/b4689395a. Those classes differ
just in the 30th line (period is omitted in newclass/b4689395a). After that
the debuggee invokes 'next' command. The test fails if
b4689395.ERROR_MESSAGE message appears in output, otherwise the test passes.
=====================================================
To reproduce :
* Go to /net/jano.sfbay/export/disk20/GammaBase/Bugs/{BugID}
* sh rerun.sh
ERROR LOGS:
----------------
#!c:/mks/mksnt/sh.exe
SystemRoot=C:/WINNT
RAS_OPTIONS=
WINDIR=C:/WINNT
PATH="Y:/st1/VM/mantis/JDK/latest/win/bin\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/src/nsk/share/lib/wintel;"
SHELL=c:/mks/mksnt/sh.exe
CLASSPATH="Y:/st1/VM/mantis/DTWS/exec1/NSK_FULLLOOK-WEEKLY-VM-ClientVM-mixed-WIN-en-2003-03-06-11-55-15-0228/work/Administrator.NT.x86/b4689395;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/src/classes\;\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/src/classes\;\;\;Y:/st1/VM/mantis/JDK/latest/win/lib/tools.jar\;\;\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a/javatest.jar\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a/classes\;Y:/st1/VM/mantis/JDK/latest/win/classes\;Y:/st1/VM/mantis/JDK/latest/win/lib/tools.jar\;\;\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a/javatest.jar\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a/classes\;Y:/st1/VM/mantis/JDK/latest/win/classes"
while [ $# -gt 0 ];
do
if [ $1 = "-jdk" ]; then
shift 1
PATH=${1}/bin;${PATH}
shift 1
fi
done
export SystemRoot
export RAS_OPTIONS
export WINDIR
export PATH
export SHELL
export CLASSPATH
#annotate TEST javaopt=-client -client -Xmixed -XX:-ShowMessageBoxOnError
Y:/st1/VM/mantis/JDK/latest/win/bin/java -client -DHANGINGJAVA1112 -client -Xmixed -XX:-ShowMessageBoxOnError b4689395 -arch=wintel -waittime=2 -debugee.vmkind=java -jdb=Y:/st1/VM/mantis/JDK/latest/win/bin/jdb "-java.options=-client -DHANGINGJAVA1112 -client -Xmixed -XX:-ShowMessageBoxOnError" -workdir=Y:/st1/VM/mantis/DTWS/exec1/NSK_FULLLOOK-WEEKLY-VM-ClientVM-mixed-WIN-en-2003-03-06-11-55-15-0228/work/Administrator.NT.x86/b4689395 -jdb.option= "-debugee.vmkeys=-client -DHANGINGJAVA1112 -client -Xmixed -XX:-ShowMessageBoxOnError -DHANGINGJAVA1112 -client -Xmixed"
##Exit status of execution step=1
##!checkExitCode
#Launching process by command line: Y:/st1/VM/mantis/JDK/latest/win/bin/jdb -J-client -J-DHANGINGJAVA1112 -J-client -J-Xmixed -J-XX:-ShowMessageBoxOnError -connect "com.sun.jdi.CommandLineLaunch:vmexec=java,options=-client -DHANGINGJAVA1112 -client -Xmixed -XX:-ShowMessageBoxOnError -DHANGINGJAVA1112 -client -Xmixed,main=b4689395a "
##>
##> WARNING: switching log to verbose mode,
##> because error is complained
##>
#launcher > Starting jdb launching local debuggee
#Creating file for jdb stdout stream: Y:/st1/VM/mantis/DTWS/exec1/NSK_FULLLOOK-WEEKLY-VM-ClientVM-mixed-WIN-en-2003-03-06-11-55-15-0228/work/Administrator.NT.x86/b4689395\jdb.stdout
#Creating file for jdb session: Y:/st1/VM/mantis/DTWS/exec1/NSK_FULLLOOK-WEEKLY-VM-ClientVM-mixed-WIN-en-2003-03-06-11-55-15-0228/work/Administrator.NT.x86/b4689395\jdb.session
#Creating file for jdb stderr stream: Y:/st1/VM/mantis/DTWS/exec1/NSK_FULLLOOK-WEEKLY-VM-ClientVM-mixed-WIN-en-2003-03-06-11-55-15-0228/work/Administrator.NT.x86/b4689395\jdb.stderr
#Setting first breakpoint
#Sending command: stop in b4689395a.main
#
#Starting debuggee class
#Sending command: run
#
#launcher > Compound prompt found: main[1]
#Test cases starts.
#Waiting for jdb exits
## ERROR: jdb did not exit after timeout.
## ERROR: Sending quit command to jdb.
#Sending command: quit
#
#
#
##>
##> SUMMARY: Following errors occured
##> during test execution:
##>
## ERROR: jdb did not exit after timeout.
## ERROR: Sending quit command to jdb.
#java.lang.IncompatibleClassChangeError
# at b4689395.runCases(b4689395.java:33)
# at nsk.share.jdb.JdbTest.runTest(JdbTest.java:78)
# at b4689395.run(b4689395.java:24)
# at b4689395.main(b4689395.java:18)
#Exception in thread "main"
Tests failed : nsk/jdb/regression/b4689395
Testbase : testbase_nsk
VM failed : server/client
Mode : -Xcomp/-Xmixed
JDK failed : 1.4.2-b18
platforms : WIN/solsparc
-----------------------------------------------------------------------------
This test passed in mantis beta b17
=====================================================
Regression test for the bug
4689395 (P4/S3) "step over" after a class is redefined acts like "step out"
Release summary: 1.4
Hardware version: generic
O/S version (unbundled products): 5.8
The test consists of two java-files:
b4689395.java - launches jdb and debuggee, writes commands to jdb,
reads the jdb output;
b4689395a.java - the debugged application.
The debugged application (b4689395a.java) defines method minor() that
prints four lines into System.out. b4689395 sets a breakpoint on the 31st
line
System.out.println("A breakpoint is here.");
and then redefines b4689395a with newclass/b4689395a. Those classes differ
just in the 30th line (period is omitted in newclass/b4689395a). After that
the debuggee invokes 'next' command. The test fails if
b4689395.ERROR_MESSAGE message appears in output, otherwise the test passes.
=====================================================
To reproduce :
* Go to /net/jano.sfbay/export/disk20/GammaBase/Bugs/{BugID}
* sh rerun.sh
ERROR LOGS:
----------------
#!c:/mks/mksnt/sh.exe
SystemRoot=C:/WINNT
RAS_OPTIONS=
WINDIR=C:/WINNT
PATH="Y:/st1/VM/mantis/JDK/latest/win/bin\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/src/nsk/share/lib/wintel;"
SHELL=c:/mks/mksnt/sh.exe
CLASSPATH="Y:/st1/VM/mantis/DTWS/exec1/NSK_FULLLOOK-WEEKLY-VM-ClientVM-mixed-WIN-en-2003-03-06-11-55-15-0228/work/Administrator.NT.x86/b4689395;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/src/classes\;\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/src/classes\;\;\;Y:/st1/VM/mantis/JDK/latest/win/lib/tools.jar\;\;\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a/javatest.jar\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a/classes\;Y:/st1/VM/mantis/JDK/latest/win/classes\;Y:/st1/VM/mantis/JDK/latest/win/lib/tools.jar\;\;\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a/javatest.jar\;Y:/st1/VM/mantis/DTWS/suites/NSK_FULLLOOK/testbase/JCKS/JCK-118a/classes\;Y:/st1/VM/mantis/JDK/latest/win/classes"
while [ $# -gt 0 ];
do
if [ $1 = "-jdk" ]; then
shift 1
PATH=${1}/bin;${PATH}
shift 1
fi
done
export SystemRoot
export RAS_OPTIONS
export WINDIR
export PATH
export SHELL
export CLASSPATH
#annotate TEST javaopt=-client -client -Xmixed -XX:-ShowMessageBoxOnError
Y:/st1/VM/mantis/JDK/latest/win/bin/java -client -DHANGINGJAVA1112 -client -Xmixed -XX:-ShowMessageBoxOnError b4689395 -arch=wintel -waittime=2 -debugee.vmkind=java -jdb=Y:/st1/VM/mantis/JDK/latest/win/bin/jdb "-java.options=-client -DHANGINGJAVA1112 -client -Xmixed -XX:-ShowMessageBoxOnError" -workdir=Y:/st1/VM/mantis/DTWS/exec1/NSK_FULLLOOK-WEEKLY-VM-ClientVM-mixed-WIN-en-2003-03-06-11-55-15-0228/work/Administrator.NT.x86/b4689395 -jdb.option= "-debugee.vmkeys=-client -DHANGINGJAVA1112 -client -Xmixed -XX:-ShowMessageBoxOnError -DHANGINGJAVA1112 -client -Xmixed"
##Exit status of execution step=1
##!checkExitCode
#Launching process by command line: Y:/st1/VM/mantis/JDK/latest/win/bin/jdb -J-client -J-DHANGINGJAVA1112 -J-client -J-Xmixed -J-XX:-ShowMessageBoxOnError -connect "com.sun.jdi.CommandLineLaunch:vmexec=java,options=-client -DHANGINGJAVA1112 -client -Xmixed -XX:-ShowMessageBoxOnError -DHANGINGJAVA1112 -client -Xmixed,main=b4689395a "
##>
##> WARNING: switching log to verbose mode,
##> because error is complained
##>
#launcher > Starting jdb launching local debuggee
#Creating file for jdb stdout stream: Y:/st1/VM/mantis/DTWS/exec1/NSK_FULLLOOK-WEEKLY-VM-ClientVM-mixed-WIN-en-2003-03-06-11-55-15-0228/work/Administrator.NT.x86/b4689395\jdb.stdout
#Creating file for jdb session: Y:/st1/VM/mantis/DTWS/exec1/NSK_FULLLOOK-WEEKLY-VM-ClientVM-mixed-WIN-en-2003-03-06-11-55-15-0228/work/Administrator.NT.x86/b4689395\jdb.session
#Creating file for jdb stderr stream: Y:/st1/VM/mantis/DTWS/exec1/NSK_FULLLOOK-WEEKLY-VM-ClientVM-mixed-WIN-en-2003-03-06-11-55-15-0228/work/Administrator.NT.x86/b4689395\jdb.stderr
#Setting first breakpoint
#Sending command: stop in b4689395a.main
#
#Starting debuggee class
#Sending command: run
#
#launcher > Compound prompt found: main[1]
#Test cases starts.
#Waiting for jdb exits
## ERROR: jdb did not exit after timeout.
## ERROR: Sending quit command to jdb.
#Sending command: quit
#
#
#
##>
##> SUMMARY: Following errors occured
##> during test execution:
##>
## ERROR: jdb did not exit after timeout.
## ERROR: Sending quit command to jdb.
#java.lang.IncompatibleClassChangeError
# at b4689395.runCases(b4689395.java:33)
# at nsk.share.jdb.JdbTest.runTest(JdbTest.java:78)
# at b4689395.run(b4689395.java:24)
# at b4689395.main(b4689395.java:18)
#Exception in thread "main"