[ros-bugs] [Bug 1263] New: KDB bugchecks with a pagefault debugging Xming hang.

ReactOS.Bugzilla at reactos.org ReactOS.Bugzilla at reactos.org
Mon Jan 9 04:08:25 CET 2006 

http://www.reactos.org/bugzilla/show_bug.cgi?id=1263

           Summary: KDB bugchecks with a pagefault debugging Xming hang.
           Product: ReactOS
           Version: TRUNK
          Platform: VMWare 5
        OS/Version: ReactOS
            Status: NEW
          Severity: critical
          Priority: P3
         Component: Kernel
        AssignedTo: ros-bugs at reactos.org
        ReportedBy: waxdragon at gmail.com
         QAContact: ros-bugs at reactos.org


Testing Xming under ros, I try to use KDB to find out why it hangs upon start. 
  I am using Xlauch to start Xming, using the "One large window" option, Display
number 0, the "Start no client" option, clipboard disabled and no additional
parameters. Xming will not draw a window, and appears to hang for a while, if
you break into kdb and attach to it, you will get the bugcheck.  100%
reproducable. This is what happens:

(lib/shell32/shelllink.c:468) (007f28a8)->(L"C:\\Documents and
Settings\\Administrator.REACTOS\\Recent\\Xlaunch.lnk.lnk")
(lib/shell32/shlexec.c:1251) flags ignored: 0x00000004
(lib/shell32/shlexec.c:1251) flags ignored: 0x00010000
(lib/ntdll/ldr/utils.c:2072) Relocating (77800000 -> 00501000)
C:\ReactOS\system32\winspool.drv
FIXME: CopyImage doesn't support IMAGE_ICON correctly!
(lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find mxdMessage
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'msacm.drv'
(Status c0000135)
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of
'midimap.drv' (Status c0000135)
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsys/win32k/ntuser/message.c:1121) Failed to copy message to kernel:
invalid usermode buffer
FIXME: CopyImage doesn't support IMAGE_ICON correctly!
(lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find mxdMessage
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'msacm.drv'
(Status c0000135)
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of
'midimap.drv' (Status c0000135)
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of
'QUSEREX.DLL' (Status c0000135)
MainFrameBase::OpenShellFolders(): parent_pidl=C:\Documents and
Settings\Administrator.REACTOS\Desktop
(lib/shell32/shlexec.c:1251) flags ignored: 0x0000000c
(lib/shell32/shlexec.c:1251) flags ignored: 0x00010000
Entered debugger on embedded INT3 at 0x0008:0x80074430.
kdb:> proc lit
ESC[7h^Eproc: 'lit' is not a valid process id!
kdb:> proc list
  PID         State       Filename
 *0x00000004  In Memory   System
  0x0000004c  In Memory   smss.exe
  0x00000068  In Memory   csrss.exe
  0x0000008c  In Memory   winlogon.exe
  0x000000a8  In Memory   services.exe
  0x000000b8  In Memory   eventlog.exe
  0x000000c4  In Memory   umpnpmgr.exe
  0x000000d4  In Memory   dhcp.exe
  0x00000100  In Memory   userinit.exe
  0x00000110  In Memory   explorer.exe
  0x000002c8  In Memory   Xlaunch.exe
  0x000002cc  In Memory   Xming.exe
  0x000002e0  In Memory   cmd.exe
  0x000002f0  In Memory   ctm.EXE
kdb:> proc
Current process:
  PID:             0x00000004
  State:           In Memory (0x0)
  Image Filename:  System
kdb:> mod
  Base      Size      Name
  80000000  001d3000  ntoskrnl.exe
  80437000  f000e739  hal.dll
  808f8000  00029000  acpi.sys
  80929000  0000a000  pci.sys
  80933000  0000a000  scsiport.sys
  8093d000  0000a000  atapi.sys
  80948000  00009000  buslogic.sys
  80a63000  00009000  class2.sys
  80a6c000  00009000  disk.sys
  80a75000  00015000  vfatfs.sys
  80a8a000  0001f000  bootvid.sys
  80aa9000  0001b000  ndis.sys
  80af8000  0000e000  VIDEOPRT.SYS
  80adc000  00003a40  vmx_svga.sys
  80b16000  0000e000  floppy.sys
  80b37000  00008000  cdrom.sys
  80b4f000  00008000  fs_rec.sys
  80b5f000  00007000  beep.sys
  80b76000  00009000  null.sys
  80b97000  0000c000  i8042prt.sys
  80bb3000  00008000  mouclass.sys
  80bcb000  00008000  kbdclass.sys
  80be3000  00007000  blue.sys
  87200000  00007000  vbemp.sys
  87217000  00009000  vgamp.sys
  87230000  00007000  msfs.sys
  87247000  00009000  npfs.sys
  8731c000  00012000  afd.sys
  9ecb0000  0005d000  freetype.dll
  9eb35000  000ab000  win32k.sys
  9ed1d000  00008000  kbdus.dll
  9f87b000  000136e0  vmx_fb.DLL
  9fd71000  0000b000  cdfs.sys
  9fec3000  0000b000  serial.sys
  9fede000  00008000  serenum.sys
  a0253000  00009000  pcnet.sys
  a02e1000  00012000  usbport.sys
  a02b2000  0000f000  usbuhci.sys
  a0357000  0000a000  usbhub.sys
kdb:> proc list
  PID         State       Filename
 *0x00000004  In Memory   System
  0x0000004c  In Memory   smss.exe
  0x00000068  In Memory   csrss.exe
  0x0000008c  In Memory   winlogon.exe
  0x000000a8  In Memory   services.exe
  0x000000b8  In Memory   eventlog.exe
  0x000000c4  In Memory   umpnpmgr.exe
  0x000000d4  In Memory   dhcp.exe
  0x00000100  In Memory   userinit.exe
  0x00000110  In Memory   explorer.exe
  0x000002c8  In Memory   Xlaunch.exe
  0x000002cc  In Memory   Xming.exe
  0x000002e0  In Memory   cmd.exe
  0x000002f0  In Memory   ctm.EXE
kdb:> proc attach 0x2cc
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0x0000003b could not be read: Page not present.
KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1242
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

Technical information:

*** STOP: 0x0000001E (0xc0000005,0x80085ab1,0x00000000,0x0000003b)

***    ntoskrnl.exe - Address 0x80085ab1 base at 0x80000000, DateStamp 0x0

Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:80085ab1 <ntoskrnl.exe:85ab1
(lib/string/i386/memcpy_asm.s:35 (memcpy))>
cr2 3b cr3 23000 Proc: 80c04c20 Pid: 4 <System> Thrd: 80c099f8 Tid: 24
DS 23 ES 23 FS 30 GS 0
EAX: 0000003b   EBX: 800ccc90   ECX: 0000001d
EDX: 00000074   EBP: 800d2170   ESI: 0000003b   ESP: 800d20f4
EDI: 800ccc90   EFLAGS: 00010016 kESP 800d20f4 kernel stack base 800cf240
Frames:
<ntoskrnl.exe:69699 (ntoskrnl/kdbg/kdb.c:0 ())>
<ntoskrnl.exe:6a75d (ntoskrnl/kdbg/kdb.c:1051 (KdbpAttachToThread))>
<ntoskrnl.exe:6a866 (ntoskrnl/kdbg/kdb.c:1110 (KdbpAttachToProcess))>
<ntoskrnl.exe:6c6ea (ntoskrnl/kdbg/kdb_cli.c:1112 (KdbpCmdProc))>
<ntoskrnl.exe:6dabc (ntoskrnl/kdbg/kdb_cli.c:2178 (KdbpDoCommand))>
<ntoskrnl.exe:6e16d (ntoskrnl/kdbg/kdb_cli.c:2238 (KdbpCliMainLoop))>
<ntoskrnl.exe:6a898 (ntoskrnl/kdbg/kdb.c:1118 (KdbpCallMainLoop))>
<ntoskrnl.exe:6960d (ntoskrnl/kdbg/i386/kdb_help.S:134 (KdbpStackSwitchAndCall))>

Entered debugger on embedded INT3 at 0x0008:0x80074436.



This is entered as a critical since it is a broken tool that is inhibiting
troubleshooting, and it's a regression.  I've talked to blight about similar
bugs, and I'm pretty sure he is not going to look into it. I can try to
regression test this, but it will take some time.

Could another developer please look into this?

-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.

More information about the Ros-bugs mailing list