A strange thing with compilation on my Intel comp & DX s

needforhint · Post by **needforhint** » Mon Dec 11, 2006 10:23 pm

just look at this picture

who doesn't know, let me tell

the memcpy() function fails permanently, debugging the code I found out this situation you can see on the picture above.
The memcpy function simply wants some .ASM source code file for who knows why, and that adresary is C/Xrend/Xrend/intel, while C/Xrend/Xrend is my project path and intel adresary doesn't exist in there.!

who wants to kill Intel? or who wants to kill Microsoft?

and how do I continue without a function to copy memory?

Saturn · Post by **Saturn** » Mon Dec 11, 2006 10:46 pm

To me this just looks as if you want not to step over memcyp but step into it. But you can't step into it as long as you don't have the source, which VS now is looking for.
So remedy would be to simply step over instead of stepping into it. The bug is more likely to be in your code than in memcpy anyway.

needforhint · Post by **needforhint** » Mon Dec 11, 2006 11:39 pm

the progress is before the memcpy, of course, becouse memcpy fails, resulting in wrong NULL memory access and a drop

Saturn · Post by **Saturn** » Tue Dec 12, 2006 12:13 am

I understand that.

But the bug in your program has nothing to do with this window popping up. That's what I meant.

Of course memcpy can fail when you provide invalid addresses or mem size. You don't check HRESULT of the last dx-call, but it looks good in the debugger, so pDestMem is likely to be valid, but what about MemSize? Maybe larger than the locked buffer? And pSourceMem?