Oh, uint32 is short from "unsigned 32bit integer". I'm a dummy, I haven't noticed.
So, the output window is from the exact code there? (With assignment not sandwiched) So... the shown value of pixels[i] should always be the same, right? But it breaks at the third attempt, so the second allocation must have overriten the bytes for pixels[3] amirite?
I'm not an expert of neither C nor Assembly, but isn't the "arrow line" missing something:
MOV *here*(&eax),&eax ? Unless it really wants to allocate the same value to itself (kind of?) , which is kind of pointless
|