Details
-
Bug
-
Resolution: Fixed
-
Major
-
0.4.13-dev-514-g3c8f19e
Description
It feels like 'bt' result regressed.
–
CORE-14094 as example:
Old:
(ntoskrnl/kd/kdio.c:105) ReactOS 0.4.8-dev (Build 20171210-0.4.8-dev-391-g197ec4c) (Commit 197ec4c5b8f807ee64f323d1461295841bd31c59)
|
...
|
kdb:> bt
|
Eip:
|
<NTOSKRNL.EXE:149fef (:0 (DbgBreakPoint))>
|
Frames:
|
<NTOSKRNL.EXE:2fe4d (ntoskrnl/include/internal/ex.h:1269 (ExAcquireFastMutexUnsafe))>
|
<vpc-8042.sys:9f5c>
|
<NTOSKRNL.EXE:6f88b (ntoskrnl/io/iomgr/irp.c:1223 (IofCallDriver))>
|
<mouclass.sys:2639 (drivers/input/mouclass/mouclass.c:863 (ClassPnp))>
|
...
|
Current:
(ntoskrnl/kd/kdio.c:106) ReactOS 0.4.14-dev (Build 20191022-0.4.14-dev-115-g4576127) (Commit 457612702b615b45436f02bb8c7eda9be4d0c47c)
|
...
|
kdb:> bt
|
Eip:
|
<ntoskrnl.exe:1564e3 (sdk/lib/rtl/i386/debug_asm.S:34 (DbgBreakPoint))>
|
Frames:
|
<ntoskrnl.exe:2f44d (ntoskrnl/include/internal/ex.h:1325 (ExAcquireFastMutexUnsafe))>
|
Couldn't access memory at 0xFCB8C4A0!
|