Really admire this article. I also saw few of your posts in individual FAQs which cleared me in many ways. Your focus on "COMMONLY KNOWN UNKNOWNS" is simply the great.
Go ahead !!. I rated excellent and thats what I could do.
I am in an very confusing situation.. and maybe you can help me.
I have a code that works fine in debug version within the VS2005 IDE but crashes when I run the debug version in the command prompt. what's even more confusing is that the release version works fine (in both IDE and command prompt)
do you have any idea what's causing this ? i have no idea how to even begin solving this !
not the appropriate place
Posted by cilu
on 07/11/2007 02:41am
This is not the appropriate place to address this questions. Ask it on a forum, such as www.codeguru.com/forum. Please post only article-related comments here. Thank you.
A pointer to the next block allocated, but next means the previous allocated block because the list is seen as a stack, with the latest allocated block at the top.
A pointer to the previous block allocated; this means the block that was allocated after the current block.
Does not it mean the same ? I mean afterall "block that was allocated after the current block" indicates the block previously allocated in stack. can u explain it in more detail?
a doubt explained
Posted by cilu
on 04/06/2005 07:07am
The names are a little bit confussing, I admit, but I was not the one to name them (blame MS for that). You have to understand that "next" and "prev" refer to the chronology. Pointer pBlockHeaderNext leads you to the block allocated before this one, chronologically. In the same way, pBlockHeaderPrev leads you to the block that was allocated after this one, chronologically. If the current block is the last allocated block, then pBlockHeaderPrev is NULL, because there is no other block subsequently allocated (on the timeline).
Hope this makes things clear.
After 7 years of experience in Windows programming. Sometimes I read papers that tell me: "OOH! You must start from scratch!".
Why I never cared these 0xCDs 0xFEEEs and ...
I always called them trash memory.
That was very good Marius. Thank you :)