JDK-6983140 : 50+ sajdi tests fail with Windbg Error: ReadVirtual failed on WinXP with JDK7-B108 Server VM
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2010-09-08
  • Updated: 2012-02-01
  • Resolved: 2010-12-21
Related Reports
Duplicate :  
JDK-6987812 - SAJDI: "gHotSpotVMTypes was not initialized properly in the remote process"
Relates :  
JDK-6983135 - 50+ sajdi tests fail with UnalignedAddressException on WinXP with JDK7-B108 Client VM
Description
During my baseline testing on JDK7-B108, 50+ VM/NSK sajdi tests failed
due to the following exception backtrace:

[2010-09-05T07:42:00.02] Caused by: sun.jvm.hotspot.debugger.DebuggerException: Windbg Error: ReadVirtual failed!
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.readBytesFromProcess0(Native Method)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.readBytesFromProcess(WindbgDebuggerLocal.java:485)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.debugger.DebuggerBase$Fetcher.fetchPage(DebuggerBase.java:76)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.debugger.PageCache.getPage(PageCache.java:178)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.debugger.PageCache.getData(PageCache.java:63)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.debugger.DebuggerBase.readBytes(DebuggerBase.java:217)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.debugger.DebuggerBase.readCInteger(DebuggerBase.java:375)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.debugger.DebuggerBase.readAddressValue(DebuggerBase.java:454)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.readAddress(WindbgDebuggerLocal.java:316)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.debugger.windbg.WindbgAddress.getAddressAt(WindbgAddress.java:72)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.HotSpotTypeDataBase.readVMTypes(HotSpotTypeDataBase.java:125)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.HotSpotTypeDataBase.<init>(HotSpotTypeDataBase.java:85)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.HotSpotAgent.setupVM(HotSpotAgent.java:388)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.HotSpotAgent.go(HotSpotAgent.java:315)
[2010-09-05T07:42:00.02]        at sun.jvm.hotspot.HotSpotAgent.attach(HotSpotAgent.java:158)


Results dir: vm-sajdi-prod-server-prod-comp.windows-i586
    executed: 93  passed: 24  ignored: 0  FAILED: 69
    UNEXPECTED: 50
    time: 21 minute(s)

Here is the list of tests:

nsk/sajdi/ArrayReference/getValue/getvalue001
nsk/sajdi/ArrayReference/getValues/getvalues001
nsk/sajdi/ArrayReference/getValues_ii/getvalues_ii001
nsk/sajdi/ClassLoaderReference/visibleClasses/vsbclasses001
nsk/sajdi/InterfaceType/superinterfaces/superintf001
nsk/sajdi/Method/allLineLocations/linelocs001
nsk/sajdi/Method/allLineLocations_ss/linelocs_ss001
nsk/sajdi/Method/bytecodes/bytecodes001
nsk/sajdi/Method/location/location001
nsk/sajdi/Method/locationsOfLine_i/locofline_i001
nsk/sajdi/Method/locationsOfLine_ssi/locofline_ssi001
nsk/sajdi/ObjectReference/getValues/getvalues001
nsk/sajdi/ObjectReference/owningThread/ownthrd002
nsk/sajdi/ReferenceType/allLineLocations/linelocs001
nsk/sajdi/ReferenceType/allLineLocations_ss/linelocs_ss001
nsk/sajdi/ReferenceType/fieldByName/fldbyname001
nsk/sajdi/ReferenceType/fields/fields001
nsk/sajdi/ReferenceType/getValues/getvalues001
nsk/sajdi/ReferenceType/locationsOfLine_i/locofline_i001
nsk/sajdi/ReferenceType/locationsOfLine_ssi/locofline_ssi001
nsk/sajdi/ReferenceType/methods/methods001
nsk/sajdi/ReferenceType/methodsByName/methbyname001
nsk/sajdi/ReferenceType/sourceDebugExtension/srcdebugx001
nsk/sajdi/SAPIDAttachingConnector/attach/attach001
nsk/sajdi/SAPIDAttachingConnector/attach/attach002
nsk/sajdi/ThreadGroupReference/threadGroups/thrdgrps001
nsk/sajdi/ThreadReference/ownedMonitors/ownmon002
nsk/sajdi/ThreadReference/status/status001
nsk/sajdi/VMCannotBeModifiedException/thrown/thrown001
nsk/sajdi/VMCannotBeModifiedException/thrown/thrown002
nsk/sajdi/VirtualMachine/allClasses/allclasses001
nsk/sajdi/VirtualMachine/allThreads/allthreads001
nsk/sajdi/VirtualMachine/canBeModified/canbemodif001
nsk/sajdi/VirtualMachine/capabilities/caps001
nsk/sajdi/VirtualMachine/capabilities/caps002
nsk/sajdi/VirtualMachine/classesByName/clsbyname001
nsk/sajdi/VirtualMachine/eventQueue/eventqueue001
nsk/sajdi/VirtualMachine/eventRequestManager/reqmgr001
nsk/sajdi/VirtualMachine/exit/exit001
nsk/sajdi/VirtualMachine/getDefaultStratum/getdfltstrat001
nsk/sajdi/VirtualMachine/mirrorOf/mirrorof001
nsk/sajdi/VirtualMachine/mirrorOf_s/mirrorof_s001
nsk/sajdi/VirtualMachine/process/process001
nsk/sajdi/VirtualMachine/redefineClasses/redefine001
nsk/sajdi/VirtualMachine/resume/resume001
nsk/sajdi/VirtualMachine/setDebugTraceMode/tracemode001
nsk/sajdi/VirtualMachine/setDefaultStratum/setdfltstrat001
nsk/sajdi/VirtualMachine/suspend/suspend001
nsk/sajdi/VirtualMachine/topLevelThreadGroups/topthrgroups001
nsk/sajdi/VirtualMachine/virtualMachine/virtmachine001

Note that the above are only the "unexpected failures". I suspect
that other tests also fail in this way, but are masked by other
entries on the fail_list.


I believe the following config fails the same test list:

Results dir: vm-sajdi-prod-server-prod-mixed.windows-i586
    executed: 93  passed: 24  ignored: 0  FAILED: 69
    UNEXPECTED: 50
    time: 22 minute(s)

Interestingly enough, the following two Server VM configs do not
have the same failures:

Results dir: vm-sajdi-prod-server-fast-comp.windows-i586
    executed: 93  passed: 89  ignored: 0  failed: 4
    time: 14 minute(s)
Results dir: vm-sajdi-prod-server-fast-mixed.windows-i586
    executed: 93  passed: 89  ignored: 0  failed: 4
    time: 14 minute(s)


The Client VM fails a similar list of tests in a different way:

    6983135 3/3 50+ sajdi tests fail with UnalignedAddressException
                on WinXP with JDK7-B108 Client VM
Here are the results for a rerun with JDK7-B107 Server VM bits:

Results dir: vm-sajdi-prod-server_b107-prod-comp.windows-i586
    executed: 93  passed: 89  ignored: 0  failed: 4
    time: 28 minute(s)
Results dir: vm-sajdi-prod-server_b107-prod-mixed.windows-i586
    executed: 93  passed: 88  ignored: 0  failed: 5
    FAILED INVALID: 1
    time: 59 minute(s)

    Failed test logs:
    test name: nsk/sajdi/SACoreAttachingConnector/transport/transport001
    log file:  vm-sajdi-prod-server_b107-prod-mixed.windows-i586/dcubed.Windows_XP.x86/transport001/transport001.log
        This is an invalid test failure:
        exit code -1073741819 caused by unknown


Summary of Test Results (2 result dirs)
=========================================
    all executed: 186  all passed: 177  all ignored: 0  all failed: 9
    FAILED INVALID: 1
    time: 1 hour(s) 27 minute(s)

    Failed test logs:
    test name: nsk/sajdi/SACoreAttachingConnector/transport/transport001
    log file:  vm-sajdi-prod-server_b107-prod-mixed.windows-i586/dcubed.Windows_XP.x86/transport001/transport001.log
        This is an invalid test failure:
        exit code -1073741819 caused by unknown
Here are the tests that fail due to 'Windbg Error: ReadVirtual failed'
on WinXP with JDK7-B108 Server VM that are obscured by other bugs on
the fail_list:

nsk/sajdi/ArrayType/componentType/comptype001
nsk/sajdi/ClassType/interfaces/interfaces001
nsk/sajdi/Method/arguments/arguments001
nsk/sajdi/Method/variables/variables001
nsk/sajdi/PathSearchingVirtualMachine/classPath/classpath001
nsk/sajdi/PrimitiveType/name/name001
nsk/sajdi/PrimitiveValue/value/value001
nsk/sajdi/ReferenceType/allFields/allfields001
nsk/sajdi/ReferenceType/allMethods/allmethods001
nsk/sajdi/ReferenceType/nestedTypes/nestedtypes001
nsk/sajdi/ReferenceType/nestedTypes/nestedtypes002
nsk/sajdi/ReferenceType/visibleFields/vsbfields001
nsk/sajdi/ReferenceType/visibleMethods/vsbmethods001
nsk/sajdi/SADebugServerAttachingConnector/attach/attach001
nsk/sajdi/SADebugServerAttachingConnector/attach/attach002
nsk/sajdi/ThreadReference/frames/frames001
nsk/sajdi/ThreadReference/status/status002
nsk/sajdi/jdb/options/connect/connect001
nsk/sajdi/jdb/options/connect/connect003
Comments
EVALUATION This bug describes a variation of the following bug: 6987812 2/3 SAJDI: "gHotSpotVMTypes was not initialized properly in the remote process" With the fix for 6987812 in place, this failure mode no longer occurs so I'm closing this bug as a duplicate of 6987812.
21-12-2010
EVALUATION A lot of tests fail, regression
15-12-2010
EVALUATION There are a total of 137 tests that fail with 'Windbg Error: ReadVirtual failed' in my JDK7-B108 Win32 baseline testing: $ grep 'Windbg Error: ReadVirtual failed' vm-sajdi-prod-server-*/dcubed*/*/*.log | wc -l 137 However, in my JDK7-B109 Win32 baseline testing, there are none: $ grep 'Windbg Error: ReadVirtual failed' vm-sajdi-prod-server-*/dcubed*/*/*.log | wc -l 0 However, there are 138 tests that fail in the mode described by 6987812: $ grep 'gHotSpotVMTypes' vm-sajdi-prod-server-*/dcubed*/*/*.log | wc -l 138
28-09-2010