[ros-bugs] [Bug 2140] lswitch crashes system

[ReactOS.Bugzilla at www.reactos.org]

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


Haos <olaf_siejka at o2.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |olaf_siejka at o2.pl




--- Comment #1 from Haos <olaf_siejka at o2.pl>  2008-01-30 02:29:23 CET ---
Used 32041 with QEMU to reproduce the error. I downloaded the built lswitch.exe
then runned it with lswitch 20 command (which was supposed to bind the
programme to capslock. Then after running the programme, i pressed capslock
once. Result:

KeBugCheckEx at ntoskrnl\ex\resource.c:1881

*** Fatal System Error: 0x000000e3 (RESOURCE_NOT_OWNED)
Address of resource: 0x9E2FE1A0,
Address of thread: 0x816548E0,
Address of owner table: 0x00000000 (doesn`t exist),
Reserved: 0x00000002,

Entered debugger on embedded INT3 at 0x0008:0x808a2338.
kdb:> bt
&#8592;[7h&#9827;Eip:
<NTOSKRNL.EXE:a2339 (lib\rtl\i386\debug_asm.S:42
(RtlpBreakWithStatusInstruction
))>
Frames:
<NTOSKRNL.EXE:29f6 (ntoskrnl/ke/bug.c:1100 (KeBugCheckWithTf at 24))>
<NTOSKRNL.EXE:2b2a (ntoskrnl/ke/bug.c:1353 (KeBugCheckEx at 20))>
<NTOSKRNL.EXE:2b2ba (ntoskrnl/ex/resource.c:1885 (@ExReleaseResourceLite at 4))>
<win32k.sys:6653e (subsystems/win32/win32k/ntuser/ntuser.c:98 (@UserLeave at 0))>
<win32k.sys:66402 (subsystems/win32/win32k/ntuser/msgqueue.c:1088
(@co_MsqSendMe
ssage at 36))>
<win32k.sys:5940b (subsystems/win32/win32k/ntuser/hook.c:294
(@co_HOOK_CallHooks
@16))>
<win32k.sys:65351 (subsystems/win32/win32k/ntuser/msgqueue.c:715
(@co_MsqPostKey
boardMessage at 12))>
<win32k.sys:5ae1f (subsystems/win32/win32k/ntuser/input.c:825
(KeyboardThreadMai
n at 4))>
<NTOSKRNL.EXE:7d183 (ntoskrnl/ps/thread.c:158 (PspSystemThreadStartup at 8))>
<NTOSKRNL.EXE:8824e (ntoskrnl\ke\i386\ctxswitch.S:306 (KiThreadStartup at 156))>


-- 
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.