PocketMatrix

I am having troubles with my game running on Dell Axim X5 devices, getting access violations like 0x80000002 address:0002042c. The address changes. Done some research, and it seems the error is related to dword boundaries or stack sizes. Has anyone delt with this before?

My stack settings are currently:
Reserve: 0x10000, Commit: 0x1000
I don't really understand what they mean, but the above address may indicate that the stack is too small, although I'm not convinced about that because I would expect to get a stack error instead. What if I just double to 0x20000 etc?

If the problem is dword boundary related where do I start looking in my code for the problem? For instance, only dword data types? Does signed/unsigned make a difference? Is it only certain types of memory access?

One thing that may be related is my generic list class that I inherit from to build list objects uses HeapAlloc() - could that have something to do with it?

I don't have an X5 to test on.

Thanks refractor. So, it doesn't just apply to dwords - when making structures it's important to have the items aligned on the same boundary as the length of the item - ie. short aligned to 2 bytes, char to 1 byte (although doesn't matter), int to 4 bytes?

The reason why I wanted everything bunched up is because I wanted the file size as small as possible, but given the above that doesn't seem possible (unless the items naturally lend themselves to a re-arrangement suiting correct boundaries as in your example).

I'll update my game and see if that works. Thanks everyone for your help.