However, it's good enough to point out most areas that you just shouldn't be messing with in VirtualAlloc(). :P
I was going through my backups and found this image. It's a "map" of the Win32 address space for an article I was writing, but never got around to finishing. There are missing details, oversimplifies the initial heap and completly ignores multithreading and the /3GB switch.
However, it's good enough to point out most areas that you just shouldn't be messing with in VirtualAlloc(). :P
However, it's good enough to point out most areas that you just shouldn't be messing with in VirtualAlloc(). :P
Previous Entry
Birthday
Next Entry
other people's code
Advertisement
Latest Entries
New bug to me
1676 views
Week/Class 9
1516 views
Week/Class 8
1554 views
Week/Class 7
1605 views
The promised files
1834 views
Week/Class 6
1300 views
Week/Session 5
1355 views
Week/Session 4
1294 views
On the soapbox
1396 views
Week/Session 3
1271 views
Advertisement