[ros-bugs] [Bug 3607] ntdll winetest file gets killed

[ReactOS.Bugzilla at www.reactos.org]

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


Goplat <mrnobo1024 at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|mrnobo1024 at yahoo.com        |ros-bugs at reactos.org
          Component|Win32                       |Kernel




--- Comment #1 from Goplat <mrnobo1024 at yahoo.com>  2008-07-30 17:11:34 CET ---
Here's the real backtrace - the user-mode function apc at 12 is being called in
kernel-mode!

Entered debugger on embedded INT3 at 0x0008:0x7c811ccf.
kdb:> bt
&#8592;[7h&#9827;Eip:
<kernel32.dll:11cd0> dll/win32/kernel32/misc/console.c:1370 (IntWriteConsole)
Frames:
<kernel32.dll:11d87> dll/win32/kernel32/misc/console.c:1436 (WriteConsoleA at 20)
<kernel32.dll:b274> dll/win32/kernel32/file/rw.c:42 (WriteFile at 20)
<msvcrt.dll:7dd1> lib/sdk/crt/stdio/file.c:2151 (_write)
<msvcrt.dll:8159> lib/sdk/crt/stdio/file.c:2463 (fwrite)
<msvcrt.dll:8304> lib/sdk/crt/stdio/file.c:3115 (vfprintf)
<msvcrt.dll:8353> lib/sdk/crt/stdio/file.c:3198 (fprintf)
<ntdll_winetest.exe:1cee8> include/reactos/wine/test.h:297 (winetest_trace)
<ntdll_winetest.exe:a19e> modules/rostests/winetests/ntdll/file.c:135 (apc at 12)
<NTOSKRNL.EXE:5176 (ntoskrnl/ke/apc.c:407 (KiDeliverApc at 12))>
<NTOSKRNL.EXE:d174 (ntoskrnl/ke/thrdschd.c:365 (@KiSwapThread at 8))>
<NTOSKRNL.EXE:106d9 (ntoskrnl/ke/wait.c:284 (KeDelayExecutionThread at 12))>
<NTOSKRNL.EXE:108e2 (ntoskrnl/ke/wait.c:804 (NtDelayExecution at 8))>
<NTOSKRNL.EXE:a063a (ntoskrnl\ke\i386\trap.s:244 (KiFastCallEntry))>
<ntdll.dll:5e0a> dll\ntdll\main\i386\dispatch.S:297 (KiFastSystemCallRet at 0)
<kernel32.dll:241e3> dll/win32/kernel32/thread/thread.c:822 (Sleep at 4)
<ntdll_winetest.exe:ae3c> modules/rostests/winetests/ntdll/file.c:169
(func_file)


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