Hi All!
Wow! Ros on ros build and I walk away come back and both consoles are gone.
Thank god for taskmgr!
It shows both cmds', ctm, and three make.exe, not running but still in memory.
Build 14598
(KERNEL32:mem/global.c:412) Memory Load: 23 (KERNEL32:mem/global.c:412) Memory Load: 23 (MSVCRT:io/open.c:103) not valid fd 0, g_fdend 5, fdinfo 7802d2f0, bucket 7802d2 f0, fdflags 0 (MSVCRT:io/open.c:700) _setmode: inval fd (0) (NTDLL:ldr/utils.c:2097) Relocating (77ed0000 -> 780000) C:\ReactOS\System32\gdi 32.dll (NTDLL:ldr/utils.c:2097) Relocating (77ed0000 -> 850000) C:\ReactOS\system32\gdi 32.dll (NTDLL:rtl/critical.c:446) Deadlock: 8517f8 Unhandled exception Address: 7c90a05c C:\ReactOS\system32\ntdll.dll CS:EIP 1b:7c90a3d2 DS 23 ES 23 FS 3b GS 23 EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000 EBP: 019afdd8 ESI: 00000000 ESP: 019afde0 EDI: 00000000 EFLAGS: 00000212 Frames: 7c900000+a05c C:\ReactOS\system32\ntdll.dll 5ffb0000+8381 C:\ReactOS\system32\win32csr.dll 5ffb0000+8eac C:\ReactOS\system32\win32csr.dll 220000+12a8f C:\ReactOS\system32\user32.dll 220000+12ced C:\ReactOS\system32\user32.dll 5ffb0000+91c4 C:\ReactOS\system32\win32csr.dll 7c800000+26554 C:\ReactOS\system32\kernel32.dll (NTDLL:rtl/critical.c:446) Deadlock: 8517f8 (ke/catch.c:191) Unhandled UserMode exception, terminating thread
Explorer is running btw, James
James Tabor wrote:
Frames: 7c900000+a05c C:\ReactOS\system32\ntdll.dll 5ffb0000+8381 C:\ReactOS\system32\win32csr.dll 5ffb0000+8eac C:\ReactOS\system32\win32csr.dll 220000+12a8f C:\ReactOS\system32\user32.dll 220000+12ced C:\ReactOS\system32\user32.dll 5ffb0000+91c4 C:\ReactOS\system32\win32csr.dll 7c800000+26554 C:\ReactOS\system32\kernel32.dll (NTDLL:rtl/critical.c:446) Deadlock: 8517f8 (ke/catch.c:191) Unhandled UserMode exception, terminating thread
Hi,
can you please determine and add the line numbers from the source files? I'm not sure but I think the first frame from win32csr.dll is guiconsole.c line #369. At this point is first acquire the GuiData->Lock and than is BeginPaint called which returns the Dc. It exist an other function (GuiConsoleUpdateBitmap), which calls first GetDc for getting a Dc and does than acquire the GuiData->Lock . This may be the problem, if the Dc management use also a lock or something similar.
I'm out of town until monday. Please be a patient if I do not answer immediately of your next mail.
- Hartmut
Hartmut Birr wrote:
James Tabor wrote:
Frames: 7c900000+a05c C:\ReactOS\system32\ntdll.dll 5ffb0000+8381 C:\ReactOS\system32\win32csr.dll 5ffb0000+8eac C:\ReactOS\system32\win32csr.dll 220000+12a8f C:\ReactOS\system32\user32.dll 220000+12ced C:\ReactOS\system32\user32.dll 5ffb0000+91c4 C:\ReactOS\system32\win32csr.dll 7c800000+26554 C:\ReactOS\system32\kernel32.dll (NTDLL:rtl/critical.c:446) Deadlock: 8517f8 (ke/catch.c:191) Unhandled UserMode exception, terminating thread
Hi,
can you please determine and add the line numbers from the source files? I'm not sure but I think the first frame from win32csr.dll is guiconsole.c line #369. At this point is first acquire the GuiData->Lock and than is BeginPaint called which returns the Dc. It exist an other function (GuiConsoleUpdateBitmap), which calls first GetDc for getting a Dc and does than acquire the GuiData->Lock . This may be the problem, if the Dc management use also a lock or something similar.
I'm out of town until monday. Please be a patient if I do not answer immediately of your next mail.
- Hartmut
ntdll rtl/critical.c:162 (RtlEnterCriticalSection) win32csr guiconsole.c:369 (GuiConsoleHandlePaint) win32csr guiconsole.c:749 (GuiConsoleWndProc)
user32 _User32CallWindowProcFromKernel@8 call 77eb1a60 _ZwCallbackReturn@12 This was a guess.
user32 Can't calc the offset.
win32csr guiconsole.c:874 (GuiConsoleGuiThread) kernel32 Thread/thread.c:75 (ThreadStartup)
Did we have radd2line code in the debugger enabled at some point, I remember seeing line numbers ref to the source code. Why is it turn off? Thanks, James
Hi James,
can you reproduce this bug always or was this a one shot bug?
- Hartmut