CallOneParam? 0x10? sometimes 0x20

[James Tabor]

I noticed this everywhere,

(subsystems/win32/win32k/objects/gdiobj.c:249) GDIOBJ_LockObj:
Attempted to lock object 0x10064, wrong reuse counter (Handle: 0x0,
Entry: 0x8)
(subsystems/win32/win32k/objects/dclife.c:726) Could not lock source DC 00010064
(subsystems/win32/win32k/ntuser/simplecall.c:349) Calling invalid
routine number 0x10 in NtUserCallOneParam(), Param=0x31

CallOneParam? Looks like a stack issue.

[James Tabor]

Look at this from bug 4292
http://www.reactos.org/bugzilla/attachment.cgi?id=5800

On Sun, Feb 20, 2011 at 6:46 PM, James Tabor <jimtabor.rosdev(a)gmail.com> wrote:
>   I noticed this everywhere,
>
>  (subsystems/win32/win32k/objects/gdiobj.c:249) GDIOBJ_LockObj:
>  Attempted to lock object 0x10064, wrong reuse counter (Handle: 0x0,
>  Entry: 0x8)
>  (subsystems/win32/win32k/objects/dclife.c:726) Could not lock source DC 00010064
>  (subsystems/win32/win32k/ntuser/simplecall.c:349) Calling invalid
>  routine number 0x10 in NtUserCallOneParam(), Param=0x31
>
>  CallOneParam? Looks like a stack issue.
>

[Giannis Adamopoulos]

The cause is r50813

>   Look at this from bug 4292
>  http://www.reactos.org/bugzilla/attachment.cgi?id=5800
>  
>  On Sun, Feb 20, 2011 at 6:46 PM, James Tabor <jimtabor.rosdev(a)gmail.com> wrote:
> >   I noticed this everywhere,
> >
> >  (subsystems/win32/win32k/objects/gdiobj.c:249) GDIOBJ_LockObj:
> >  Attempted to lock object 0x10064, wrong reuse counter (Handle: 0x0,
> >  Entry: 0x8)
> >  (subsystems/win32/win32k/objects/dclife.c:726) Could not lock source DC 00010064
> >  (subsystems/win32/win32k/ntuser/simplecall.c:349) Calling invalid
> >  routine number 0x10 in NtUserCallOneParam(), Param=0x31
> >
> >  CallOneParam? Looks like a stack issue.
> >  
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev