Comments on: Beware of what you get when locking DirectX Resources Buffers http://entland.homelinux.com/blog/2006/01/30/beware-of-what-you-get-when-locking-directx-resources-buffers/ Code, 3D, Games, Linux and much more... Mon, 09 Nov 2009 03:12:38 +0100 http://wordpress.org/?v=2.8.5 hourly 1 By: chanka http://entland.homelinux.com/blog/2006/01/30/beware-of-what-you-get-when-locking-directx-resources-buffers/comment-page-1/#comment-23 chanka Wed, 01 Feb 2006 06:19:21 +0000 http://entland.homelinux.com/blog/?p=49#comment-23 Yes ninja 8) Yes ninja 8)

]]> By: ent http://entland.homelinux.com/blog/2006/01/30/beware-of-what-you-get-when-locking-directx-resources-buffers/comment-page-1/#comment-22 ent Wed, 01 Feb 2006 01:18:45 +0000 http://entland.homelinux.com/blog/?p=49#comment-22 Hmmm, yes. You are right, both fourth and second solution have the same problem. try...catch seems to be the only real solution to this problem. :-\ Hmmm, yes. You are right, both fourth and second solution have the same problem. try…catch seems to be the only real solution to this problem. :-\

]]> By: chanka http://entland.homelinux.com/blog/2006/01/30/beware-of-what-you-get-when-locking-directx-resources-buffers/comment-page-1/#comment-21 chanka Tue, 31 Jan 2006 14:13:43 +0000 http://entland.homelinux.com/blog/?p=49#comment-21 I mean, if the IsBadWritePtr() return true, and after the call the memory is invalidated. I mean, if the IsBadWritePtr() return true, and after the call the memory is invalidated.

]]> By: ent http://entland.homelinux.com/blog/2006/01/30/beware-of-what-you-get-when-locking-directx-resources-buffers/comment-page-1/#comment-20 ent Tue, 31 Jan 2006 09:55:12 +0000 http://entland.homelinux.com/blog/?p=49#comment-20 IsBadWritePtr() won't return you a pointer. It returns a bool indicating if the memory pointer is writable or not. BOOL IsBadWritePtr(LPVOID lp, UINT_PTR ucb); IsBadWritePtr() won’t return you a pointer. It returns a bool indicating if the memory pointer is writable or not.

BOOL IsBadWritePtr(LPVOID lp, UINT_PTR ucb);

]]> By: chanka http://entland.homelinux.com/blog/2006/01/30/beware-of-what-you-get-when-locking-directx-resources-buffers/comment-page-1/#comment-18 chanka Tue, 31 Jan 2006 09:16:25 +0000 http://entland.homelinux.com/blog/?p=49#comment-18 >> Use the IsBadWritePtr function against the pointers returned by the DirectX API and if you get a bad pointer return a pointer to a dummy memory block internally allocated by you. To me, this is the cleanest and safest option. You should return a memory block long enough to hold the size requested by the Lock. What if the pointer is invalid after the call to IsBadWritePtr? >> Use the IsBadWritePtr function against the pointers returned by the DirectX API and if you get a bad pointer return a pointer to a dummy memory block internally allocated by you. To me, this is the cleanest and safest option. You should return a memory block long enough to hold the size requested by the Lock.

What if the pointer is invalid after the call to IsBadWritePtr?

]]>