-
Bug
-
Resolution: Future Project
-
P4
-
1.4.1, 1.4.2, 5.0, 9
-
x86
-
windows_nt, windows_2000
Name: dkR10014 Date: 04/30/2002
The following nsk test fails:
nsk/jdb/exclude/exclude001
OS: Windows NT 4.0, Windows 2000
JDK builds: jdk1.4.1-beta-b10, jdk1.4.0-b92
VMs : Client, Server
VM mode: mixed, comp, int
The test fails with error message:
## ERROR: Cought unexpected exception while executing the test: nsk.share.Failure:
Attempt to send command :untrace methods 0x14f to terminated jdb.
## ERROR: TEST FAILED
This test failure is caused by abnormal debugged VM's termination.
If the debugged application runs on java_g, then the following assertion is
hitted :
Assertion failed: (char*)p >= sbrk_base, file ../../../src/share/back/dlAlloc.c, line 496
The application has been disconnected
Being run on java, the debugged Server VM when crashing intermittently
outputs this error message:
> An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6D267415
Function=[Unknown.]
Library=h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\jdwp.dll
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
at nsk.jdb.exclude.MyThread.run(exclude001a.java:68)
Dynamic libraries:
0x00400000 - 0x00406000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\java.exe
0x77F60000 - 0x77FBE000 C:\WINNT\System32\ntdll.dll
0x77DC0000 - 0x77DFF000 C:\WINNT\system32\ADVAPI32.dll
0x77F00000 - 0x77F5E000 C:\WINNT\system32\KERNEL32.dll
0x77E70000 - 0x77EC5000 C:\WINNT\system32\USER32.dll
0x77ED0000 - 0x77EFC000 C:\WINNT\system32\GDI32.dll
0x77E10000 - 0x77E67000 C:\WINNT\system32\RPCRT4.dll
0x78000000 - 0x78040000 C:\WINNT\system32\MSVCRT.dll
0x6D320000 - 0x6D442000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\client\jvm.dll
0x77FD0000 - 0x77FFA000 C:\WINNT\System32\WINMM.dll
0x77FC0000 - 0x77FC8000 C:\WINNT\System32\mmdrv.dll
0x6BD00000 - 0x6BD21000 C:\WINNT\System32\cwbaudll.dll
0x6D1D0000 - 0x6D1D7000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\hpi.dll
0x6D2F0000 - 0x6D2FD000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\verify.dll
0x6D210000 - 0x6D228000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\java.dll
0x6D310000 - 0x6D31D000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\zip.dll
0x6D260000 - 0x6D27C000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\jdwp.dll
0x6D160000 - 0x6D166000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\dt_shmem.dll
0x6D2C0000 - 0x6D2CE000 H:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\net.dll
0x776D0000 - 0x776D8000 C:\WINNT\system32\WSOCK32.dll
0x776B0000 - 0x776C4000 C:\WINNT\system32\WS2_32.dll
0x776A0000 - 0x776A7000 C:\WINNT\system32\WS2HELP.dll
0x7A400000 - 0x7A409000 C:\WINNT\SYSTEM32\SUNWNIS.DLL
0x0F0E0000 - 0x0F136000 C:\WINNT\System32\SUNWNSL.dll
0x779D0000 - 0x779E5000 C:\WINNT\System32\MSVCRT40.dll
0x780A0000 - 0x780B2000 C:\WINNT\System32\MSVCIRT.dll
0x74FF0000 - 0x74FFE000 C:\WINNT\System32\rnr20.dll
0x77BF0000 - 0x77BF7000 C:\WINNT\System32\rpcltc1.dll
0x76AC0000 - 0x76ADD000 C:\WINNT\System32\imagehlp.dll
0x731B0000 - 0x731BA000 C:\WINNT\System32\PSAPI.DLL
Local Time = Tue Apr 30 11:59:48 2002
Elapsed Time = 100
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.4.1-beta-b10 mixed mode)
#
# An error report file has been saved as hs_err_pid249.log.
# Please refer to the file for further information.
#
The test logs these error message in jdb.stdout and jdb.session files.
Below is jdb.session file which contains commands and jdb's replies
on them:
------------------------------------------------------------------
Initializing jdb ...
> stop in nsk.jdb.exclude.exclude001a.main
Deferring breakpoint nsk.jdb.exclude.exclude001a.main.
It will be set after the class is loaded.
> run
run nsk.jdb.exclude.exclude001a
>
VM Started: Set deferred breakpoint nsk.jdb.exclude.exclude001a.main
Breakpoint hit: "thread=main", nsk.jdb.exclude.exclude001a.main(), line=19 bci=0
main[1] stop in nsk.jdb.exclude.exclude001a.lastBreak
Set breakpoint nsk.jdb.exclude.exclude001a.lastBreak
main[1] exclude
java.*,javax.*,sun.*,com.sun.*,
main[1] cont
>
Breakpoint hit: "thread=MyThread-0", nsk.jdb.exclude.exclude001a.lastBreak(), line=23 bci=0
MyThread-0[1] threads
Group system:
(java.lang.ref.Reference$ReferenceHandler)0xf7 Reference Handler cond. waiting
(java.lang.ref.Finalizer$FinalizerThread)0xf6 Finalizer cond. waiting
(java.lang.Thread)0xf5 Signal Dispatcher running
Group main:
(java.lang.Thread)0x1 main cond. waiting
(java.util.logging.LogManager$Cleaner)0x143 Thread-0 unknown
(nsk.share.Finalizer$FinalizerThread)0x144 Thread-1 unknown
(nsk.jdb.exclude.MyThread)0x140 MyThread-0 running (at breakpoint)
MyThread-0[1] step
>
Step completed: "thread=MyThread-0", nsk.jdb.exclude.MyThread.run(), line=68 bci=3
MyThread-0[1] trace methods 0x140
MyThread-0[1] cont
>
Method exited: nsk.jdb.exclude.MyThread.run "thread=MyThread-0", nsk.jdb.exclude.MyThread.run(), line=71 bci=11
MyThread-0[1] exclude java.*,javax.*,sun.*,com.sun.*,
MyThread-0[1] untrace methods 0x140
MyThread-0[1] cont
>
Breakpoint hit: "thread=MyThread-1", nsk.jdb.exclude.exclude001a.lastBreak(), line=23 bci=0
MyThread-1[1] threads
Group system:
(java.lang.ref.Reference$ReferenceHandler)0xf7 Reference Handler cond. waiting
(java.lang.ref.Finalizer$FinalizerThread)0xf6 Finalizer cond. waiting
(java.lang.Thread)0xf5 Signal Dispatcher running
Group main:
(java.lang.Thread)0x1 main cond. waiting
(java.util.logging.LogManager$Cleaner)0x143 Thread-0 unknown
(nsk.share.Finalizer$FinalizerThread)0x144 Thread-1 unknown
(nsk.jdb.exclude.MyThread)0x19f MyThread-1 running (at breakpoint)
MyThread-1[1] step
[Debugged VM's crash message was logged here.]
The application has been disconnected
exclude javax.*,sun.*,com.sun.*
> trace methods 0x19f
------------------------------------------------------------------
Test description:
The test checks jdb's 'exclude' command.
The debugged application (exclude001a.java) consecutevely creates three additional threads.
The 'run' method of these threads invokes java.lang.System.currentTimeMillis() and
com.sun.jdi.Bootstrap.virtualMachineManager() methods. For each test case the correspondent
MyThread thread is started and suspended at a breakpoint. Then method tracing is turned on with
'trace methods <thread id>' command with various exclude filtering.
How to reproduce failure:
1. cd /net/sqesvr.sfbay/export/vsn/GammaBase/Bugs/{this_bug_number}
2. sh doit.sh <JAVA_HOME> <DEBUGGED_VM_OPTIONS>
where <DEBUGGED_VM_OPTIONS> should contain -Xcomp option.
If you wish to use java_g as debugged VM then change the option to
-debugee.vmkind=java_g at command line 47 of doit.sh.
The test will appear in the next testbase_nsk r14 release.
======================================================================
The following nsk test fails:
nsk/jdb/exclude/exclude001
OS: Windows NT 4.0, Windows 2000
JDK builds: jdk1.4.1-beta-b10, jdk1.4.0-b92
VMs : Client, Server
VM mode: mixed, comp, int
The test fails with error message:
## ERROR: Cought unexpected exception while executing the test: nsk.share.Failure:
Attempt to send command :untrace methods 0x14f to terminated jdb.
## ERROR: TEST FAILED
This test failure is caused by abnormal debugged VM's termination.
If the debugged application runs on java_g, then the following assertion is
hitted :
Assertion failed: (char*)p >= sbrk_base, file ../../../src/share/back/dlAlloc.c, line 496
The application has been disconnected
Being run on java, the debugged Server VM when crashing intermittently
outputs this error message:
> An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6D267415
Function=[Unknown.]
Library=h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\jdwp.dll
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
at nsk.jdb.exclude.MyThread.run(exclude001a.java:68)
Dynamic libraries:
0x00400000 - 0x00406000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\java.exe
0x77F60000 - 0x77FBE000 C:\WINNT\System32\ntdll.dll
0x77DC0000 - 0x77DFF000 C:\WINNT\system32\ADVAPI32.dll
0x77F00000 - 0x77F5E000 C:\WINNT\system32\KERNEL32.dll
0x77E70000 - 0x77EC5000 C:\WINNT\system32\USER32.dll
0x77ED0000 - 0x77EFC000 C:\WINNT\system32\GDI32.dll
0x77E10000 - 0x77E67000 C:\WINNT\system32\RPCRT4.dll
0x78000000 - 0x78040000 C:\WINNT\system32\MSVCRT.dll
0x6D320000 - 0x6D442000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\client\jvm.dll
0x77FD0000 - 0x77FFA000 C:\WINNT\System32\WINMM.dll
0x77FC0000 - 0x77FC8000 C:\WINNT\System32\mmdrv.dll
0x6BD00000 - 0x6BD21000 C:\WINNT\System32\cwbaudll.dll
0x6D1D0000 - 0x6D1D7000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\hpi.dll
0x6D2F0000 - 0x6D2FD000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\verify.dll
0x6D210000 - 0x6D228000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\java.dll
0x6D310000 - 0x6D31D000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\zip.dll
0x6D260000 - 0x6D27C000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\jdwp.dll
0x6D160000 - 0x6D166000 h:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\dt_shmem.dll
0x6D2C0000 - 0x6D2CE000 H:\ld24\java\hotspot\jdk1.4.1\win\jre\bin\net.dll
0x776D0000 - 0x776D8000 C:\WINNT\system32\WSOCK32.dll
0x776B0000 - 0x776C4000 C:\WINNT\system32\WS2_32.dll
0x776A0000 - 0x776A7000 C:\WINNT\system32\WS2HELP.dll
0x7A400000 - 0x7A409000 C:\WINNT\SYSTEM32\SUNWNIS.DLL
0x0F0E0000 - 0x0F136000 C:\WINNT\System32\SUNWNSL.dll
0x779D0000 - 0x779E5000 C:\WINNT\System32\MSVCRT40.dll
0x780A0000 - 0x780B2000 C:\WINNT\System32\MSVCIRT.dll
0x74FF0000 - 0x74FFE000 C:\WINNT\System32\rnr20.dll
0x77BF0000 - 0x77BF7000 C:\WINNT\System32\rpcltc1.dll
0x76AC0000 - 0x76ADD000 C:\WINNT\System32\imagehlp.dll
0x731B0000 - 0x731BA000 C:\WINNT\System32\PSAPI.DLL
Local Time = Tue Apr 30 11:59:48 2002
Elapsed Time = 100
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.4.1-beta-b10 mixed mode)
#
# An error report file has been saved as hs_err_pid249.log.
# Please refer to the file for further information.
#
The test logs these error message in jdb.stdout and jdb.session files.
Below is jdb.session file which contains commands and jdb's replies
on them:
------------------------------------------------------------------
Initializing jdb ...
> stop in nsk.jdb.exclude.exclude001a.main
Deferring breakpoint nsk.jdb.exclude.exclude001a.main.
It will be set after the class is loaded.
> run
run nsk.jdb.exclude.exclude001a
>
VM Started: Set deferred breakpoint nsk.jdb.exclude.exclude001a.main
Breakpoint hit: "thread=main", nsk.jdb.exclude.exclude001a.main(), line=19 bci=0
main[1] stop in nsk.jdb.exclude.exclude001a.lastBreak
Set breakpoint nsk.jdb.exclude.exclude001a.lastBreak
main[1] exclude
java.*,javax.*,sun.*,com.sun.*,
main[1] cont
>
Breakpoint hit: "thread=MyThread-0", nsk.jdb.exclude.exclude001a.lastBreak(), line=23 bci=0
MyThread-0[1] threads
Group system:
(java.lang.ref.Reference$ReferenceHandler)0xf7 Reference Handler cond. waiting
(java.lang.ref.Finalizer$FinalizerThread)0xf6 Finalizer cond. waiting
(java.lang.Thread)0xf5 Signal Dispatcher running
Group main:
(java.lang.Thread)0x1 main cond. waiting
(java.util.logging.LogManager$Cleaner)0x143 Thread-0 unknown
(nsk.share.Finalizer$FinalizerThread)0x144 Thread-1 unknown
(nsk.jdb.exclude.MyThread)0x140 MyThread-0 running (at breakpoint)
MyThread-0[1] step
>
Step completed: "thread=MyThread-0", nsk.jdb.exclude.MyThread.run(), line=68 bci=3
MyThread-0[1] trace methods 0x140
MyThread-0[1] cont
>
Method exited: nsk.jdb.exclude.MyThread.run "thread=MyThread-0", nsk.jdb.exclude.MyThread.run(), line=71 bci=11
MyThread-0[1] exclude java.*,javax.*,sun.*,com.sun.*,
MyThread-0[1] untrace methods 0x140
MyThread-0[1] cont
>
Breakpoint hit: "thread=MyThread-1", nsk.jdb.exclude.exclude001a.lastBreak(), line=23 bci=0
MyThread-1[1] threads
Group system:
(java.lang.ref.Reference$ReferenceHandler)0xf7 Reference Handler cond. waiting
(java.lang.ref.Finalizer$FinalizerThread)0xf6 Finalizer cond. waiting
(java.lang.Thread)0xf5 Signal Dispatcher running
Group main:
(java.lang.Thread)0x1 main cond. waiting
(java.util.logging.LogManager$Cleaner)0x143 Thread-0 unknown
(nsk.share.Finalizer$FinalizerThread)0x144 Thread-1 unknown
(nsk.jdb.exclude.MyThread)0x19f MyThread-1 running (at breakpoint)
MyThread-1[1] step
[Debugged VM's crash message was logged here.]
The application has been disconnected
exclude javax.*,sun.*,com.sun.*
> trace methods 0x19f
------------------------------------------------------------------
Test description:
The test checks jdb's 'exclude' command.
The debugged application (exclude001a.java) consecutevely creates three additional threads.
The 'run' method of these threads invokes java.lang.System.currentTimeMillis() and
com.sun.jdi.Bootstrap.virtualMachineManager() methods. For each test case the correspondent
MyThread thread is started and suspended at a breakpoint. Then method tracing is turned on with
'trace methods <thread id>' command with various exclude filtering.
How to reproduce failure:
1. cd /net/sqesvr.sfbay/export/vsn/GammaBase/Bugs/{this_bug_number}
2. sh doit.sh <JAVA_HOME> <DEBUGGED_VM_OPTIONS>
where <DEBUGGED_VM_OPTIONS> should contain -Xcomp option.
If you wish to use java_g as debugged VM then change the option to
-debugee.vmkind=java_g at command line 47 of doit.sh.
The test will appear in the next testbase_nsk r14 release.
======================================================================