[ros-bugs] [Bug 4143] Fix for BitBlt, TransparentBlt, MaskBlt

[ReactOS.Bugzilla at www.reactos.org]

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


towerr <tower at reactos.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tower at reactos.org
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID




--- Comment #3 from towerr <tower at reactos.org>  2009-02-08 03:32:11 CET ---
looks like a spam, yet even no ideas i have for thoses pictures, because the
problem isn't solved with applyed a patch, so guys look twice before commit a
patch which presented here :(


--- Comment #4 from towerr <tower at reactos.org>  2009-02-08 03:34:14 CET ---
looks like a spam, yet even no ideas i have for thoses pictures, because the
problem isn't solved with applyed a patch, so guys look twice before commit a
patch which presented here :(


--- Comment #5 from towerr <tower at reactos.org>  2009-02-08 04:12:02 CET ---
-WHF?!  after this patch:

*** Fatal System Error: 0x0000001e
                       (0xC0000094,0x9F95AC14,0x9EED0740,0x00000000)

Entered debugger on embedded INT3 at 0x0008:0x808c1388.
kdb:> bt
Eip:
<NTOSKRNL.EXE:c1389 (lib\rtl\i386\debug_asm.S:42
(RtlpBreakWithStatusInstruction))>
Frames:
<NTOSKRNL.EXE:65fd (ntoskrnl/ke/bug.c:1089 (KeBugCheckWithTf at 24))>
<NTOSKRNL.EXE:68a9 (ntoskrnl/ke/bug.c:1400 (KeBugCheck at 4))>
<NTOSKRNL.EXE:2e21 (ntoskrnl/ke/i386/exp.c:1011 (_SEHExcept.34419))>
<NTOSKRNL.EXE:ba35c (ntoskrnl\ke\i386\trap.s:638 (CommonDispatchException))>
<win32k.sys:87c14 (subsystems/win32/win32k/objects/bitblt.c:889
(NtGdiStretchBlt at 48))>
<NTOSKRNL.EXE:b9a6c (ntoskrnl\ke\i386\trap.s:244 (KiFastCallEntry))>

looooook:
(subsystems/win32/win32k/objects/bitblt.c:889 (NtGdiStretchBlt at 48))


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