Cheat Engine

[flarn2006]

Why is allocateSharedMemory sometimes returning the address to memory that was already allocated in a previous call? How do I prevent it from doing so and force it to allocate a new block of memory, even if one was previously allocated with the same size?

I remember once I was allocating memory for some ASM code that's run every frame, and in another part of my Lua script I allocated some memory for storing strings. As soon as I tried to write a string to the memory I allocated for that purpose, the program crashed. What happened? It had returned the address of the memory block I allocated for code, and it just wrote the strings right over the code. Of course, it then tried to execute the string as code and promptly crashed.

How do I prevent this? On the wiki article for allocateSharedMemory it mentions something about "if it doesn't exist yet" and "if there is no shared region with this name", but I don't see anywhere to specify a name.

All I want to do is allocate some memory that's guaranteed not to already be used by something else. Is there something I'm missing?

[Dark Byte]

The function declaration in the wiki was wrong, it's allocateSharedMemory(name, size)
Where name is a unique name

Anyhow, shared memory is probably not what you want, unless you're debugging. (Shared memory retains the contents even if the game has crashed to desktop, so if you reopen the game, allocate the same name again, the original contents will be there)

currently there isn't a lua specific allocation method, but you can use this function

[flarn2006]

Well actually allocateSharedMemory sounds like it would be perfect for what I need. Thanks!