13 Mar
2025
13 Mar
'25
2:57 p.m.
On Thu Mar 13 14:51:47 2025 +0000, Jacek Caban wrote:
Thread B updates handle 123 object which gets moved to offset 789 for
whatever reason (needs growing, etc) Replacing shared object placement seems redundant. Why would it need to grow?
Why would it not? NtUserSetCursorIconData for instance seems to be able to add a variable number of frames to an existing HCURSOR object.
Requiring object size to be immutable is quite a strong requirement which isn't necessary with the existing object validation mechanism. I really don't see the point in implementing a different object validation mechanism that support only a subset of what the existing one can do.