Re: [ros-dev] buildbot exception in ReactOS on Windows_AMD64_1 VBox-Test

Looks like the crash had locked up the VM hard:

loader.c:1019: Test failed: wrong section data
(..\..\dll\ntdll\ldr\ldrutils.c:1322) LDR: LdrpMapDll Relocating Image
Name C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ldr3C.tmp (10000000 -> 00011000)
(..\..\dll\ntdll\ldr\ldrutils.c:1361) Overlapping DLL: Dynamically
Allocated Memory
loader.c:599: Test failed: got 0x4 != expected 0x1
loader.c:601: Test failed: 0x4 != PAGE_EXECUTE_WRITECOPY
loader.c:627: Test failed: got 0x4 != expected 0x1
loader.c:629: Test failed: 0x4 != PAGE_EXECUTE_WRITECOPY
loader.c:645: Test failed: got 0x4 != expected 0x1
loader.c:647: Test failed: 0x4 != PAGE_EXECUTE_WRITECOPY
(..\..\ntoskrnl\mm\ARM3\expool.c:274) Entry BlockSize 2, tag fPsR.
NextEntry PreviousSize 0, tag 

*** Fatal System Error: 0x00000019
                       (0x00000005,0xB0A0EB18,0x00000116,0xB0A0EB08)

Entered debugger on embedded INT3 at 0x0008:0x8091ba34.
kdb:> bt
Eip:
<NTOSKRNL.EXE:11ba35 (..\..\lib\rtl\i386\debug_asm.S:46
(_RtlpBreakWithStatusInstruction@0))>
Frames:
<NTOSKRNL.EXE:80445 (../../ntoskrnl/ke/bug.c:1081
(KeBugCheckWithTf@24))>
<NTOSKRNL.EXE:80581 (../../ntoskrnl/ke/bug.c:1405 (KeBugCheckEx@20))>
<NTOSKRNL.EXE:964e2 (../../ntoskrnl/mm/ARM3/expool.c:211
(ExpCheckPoolHeader@4))>
<NTOSKRNL.EXE:966d3 (../../ntoskrnl/mm/ARM3/expool.c:303
(ExpCheckPoolBlocks@4))>
<NTOSKRNL.EXE:96fa5 (../../ntoskrnl/mm/ARM3/expool.c:2215
(ExFreePoolWithTag@8))>
<NTOSKRNL.EXE:9755a (../../ntoskrnl/mm/ARM3/expool.c:2359
(ExFreePool@4))>
<NTOSKRNL.EXE:bf8da (../../ntoskrnl/mm/freelist.c:556
(MmDereferencePage@4))>
<NTOSKRNL.EXE:bf541 (../../ntoskrnl/mm/balance.c:130
(MmReleasePageMemoryConsumer@8))>
<NTOSKRNL.EXE:473b (../../ntoskrnl/cc/view.c:913 (CcFreeCachePage))>
<NTOSKRNL.EXE:c1501 (../../ntoskrnl/mm/marea.c:745
(MmFreeMemoryArea@16))>
<NTOSKRNL.EXE:413c (../../ntoskrnl/cc/view.c:962
(CcRosInternalFreeCacheSegment))>
<NTOSKRNL.EXE:6f3d (../../ntoskrnl/cc/view.c:1145
(CcRosDeleteFileCache@8))>
<NTOSKRNL.EXE:755f (../../ntoskrnl/cc/view.c:1210
(CcRosDereferenceCache@4))>
<NTOSKRNL.EXE:cb47c (../../ntoskrnl/mm/section.c:2672
(MmpDeleteSection@4))>
<NTOSKRNL.EXE:da087 (../../ntoskrnl/ob/oblife.c:211
(ObpDeleteObject@8))>
<NTOSKRNL.EXE:da11b (../../ntoskrnl/ob/oblife.c:238 (ObpReapObject@4))>
<NTOSKRNL.EXE:41e42 (../../ntoskrnl/ex/work.c:162
(ExpWorkerThreadEntryPoint@4))>
<NTOSKRNL.EXE:f2ca9 (../../ntoskrnl/ps/thread.c:156
(PspSystemThreadStartup@8))>
<NTOSKRNL.EXE:103c27 (../../ntoskrnl/ke/i386/thrdini.c:78
(KiThreadStartup@0))>
<NTOSKRNL.EXE:f2c4f (../../ntoskrnl/ps/thread.c:625
(PsCreateSystemThread@28))>--- Press q to abort, any other key to
continue ---

<f88b3db8>
<NTOSKRNL.EXE:85cc0 (../../ntoskrnl/ke/queue.c:401 (KeRemoveQueue@12))>
<NTOSKRNL.EXE:41df0 (../../ntoskrnl/ex/work.c:145
(ExpWorkerThreadEntryPoint@4))>
<NTOSKRNL.EXE:f2ca9 (../../ntoskrnl/ps/thread.c:156
(PspSystemThreadStartup@8))>
<NTOSKRNL.EXE:103c27 (../../ntoskrnl/ke/i386/thrdini.c:78
(KiThreadStartup@0))>
<NTOSKRNL.EXE:f2c4f (../../ntoskrnl/ps/thread.c:625
(PsCreateSystemThread@28))>
<f88b7db8>
<NTOSKRNL.EXE:85cc0 (../../ntoskrnl/ke/queue.c:401 (KeRemoveQueue@12))>
<NTOSKRNL.EXE:41df0 (../../ntoskrnl/ex/work.c:145
(ExpWorkerThreadEntryPoint@4))>
<NTOSKRNL.EXE:f2ca9 (../../ntoskrnl/ps/thread.c:156
(PspSystemThreadStartup@8))>
<NTOSKRNL.EXE:103c27 (../../ntoskrnl/ke/i386/thrdini.c:78
(KiThreadStartup@0))>
<NTOSKRNL.EXE:f2c4f (../../ntoskrnl/ps/thread.c:625
(PsCreateSystemThread@28))>
<f88bbdb8>
<NTOSKRNL.EXE:85cc0 (../../ntoskrnl/ke/queue.c:401 (KeRemoveQueue@12))>
<NTOSKRNL.EXE:41df0 (../../ntoskrnl/ex/work.c:145
(ExpWorkerThreadEntryPoint@4))>
<NTOSKRNL.EXE:f2ca9 (../../ntoskrnl/ps/thread.c:156
(PspSystemThreadStartup@8))>
<NTOSKRNL.EXE:103c27 (../../ntoskrnl/ke/i386/thrdini.c:78
(KiThreadStartup@0))>
<NTOSKRNL.EXE:f2c4f (../../ntoskrnl/ps/thread.c:625
(PsCreateSystemThread@28))>
<f889bdb8>
<NTOSKRNL.EXE:85cc0 (../../ntoskrnl/ke/queue.c:401 (KeRemoveQueue@12))>
<NTOSKRNL.EXE:41df0 (../../ntoskrnl/ex/work.c:145
(ExpWorkerThreadEntryPoint@4))>--- Press q to abort, any other key to
continue ---

<NTOSKRNL.EXE:f2ca9 (../../ntoskrnl/ps/thread.c:156
(PspSystemThreadStartup@8))>
<NTOSKRNL.EXE:103c27 (../../ntoskrnl/ke/i386/thrdini.c:78
(KiThreadStartup@0))>
<NTOSKRNL.EXE:f2c4f (../../ntoskrnl/ps/thread.c:625
(PsCreateSystemThread@28))>
<415c6d6d>
Couldn't access memory at 0x5C6C6E76!
kdb:>

On Thu, Jun 7, 2012, at 06:23 PM, buildbot(a)reactos.org wrote:
>   The Buildbot has finished a build on builder
> Windows_AMD64_1 VBox-Test
>  while building ReactOS.
>  Full details are available at:
>   http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/5866
>  
>  Buildbot URL: http://build.reactos.org/
>  
>  Buildslave for this Build: Windows_AMD64_2
>  
>  Build Reason: Triggerable(Windows_AMD64_1 VBox-Test Trigger)
>  Build Source Stamp: 56702
>  Blamelist: ekohl
>  
>  BUILD FAILED: exception test
>  
>  sincerely,
>   -The Buildbot
>   

-- 
With best regards
Caemyr