Re: [ros-dev] Both CMD Consoles Go Puff!

[James Tabor]

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