Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
Operating System: ReactOS
Platform: x86 Hardware
Description
I enabled the msvcrt debugchannel by doing set DEBUGCHANNEL=+msvcrt and started an application which produces some not yet known exception in msvcrt. The expected debug output never arrived, because the debug string function uses a trace which calls the debug string function again -> endless loop, which leads to a page fault in the end.
Backtrace of the behaviour:
Entered debugger on first-chance exception (Exception Code: 0xc0000005) (Page Fault)
Memory at 0x00DCFFF8 could not be written: Page not present.
kdb:> bt
Eip:
<msvcrt.dll:17420> lib/sdk/crt/string/wcs.c:750 (_vsnprintf)
Frames:
<msvcrt.dll:1d9e1> lib/3rdparty/libwine/debug.c:390 (default_dbg_vprintf)
<msvcrt.dll:1dd8d> lib/3rdparty/libwine/debug.c:212 (wine_dbg_printf)
<msvcrt.dll:1dde0> lib/3rdparty/libwine/debug.c:401 (default_dbg_vlog)
<msvcrt.dll:1e1e7> lib/3rdparty/libwine/debug.c:245 (wine_dbg_log)
<msvcrt.dll:16bbc> lib/sdk/crt/string/wcs.c:513 (pf_vsnprintf)
<msvcrt.dll:1746e> lib/sdk/crt/string/wcs.c:760 (_vsnprintf)
<msvcrt.dll:1d9e1> see first frame...
<msvcrt.dll:1dd8d>
<msvcrt.dll:1dde0>
<msvcrt.dll:1e1e7>
<msvcrt.dll:16bbc>
<msvcrt.dll:1746e>
<msvcrt.dll:1d9e1> see first frame...
<msvcrt.dll:1dd8d>
<msvcrt.dll:1dde0>
<msvcrt.dll:1e1e7>
<msvcrt.dll:16bbc>
<msvcrt.dll:1746e>
<msvcrt.dll:1d9e1> see first frame...
<msvcrt.dll:1dd8d>
...