Hi guys,

I've experienced the following strange behaviour.
I have the same code and the same openssl build.
With x64 everything I fine, but with x86 build not.
With a 32bit environment I got the following access vialotion.
I read that windows marks a freed pointer as "0XDDDDDDDD", but we are usally 
freeing and setting NULL value to a pointer, therefore a following NULL check 
later for a already freed pointer would NOT work, right?
Has anybody an adivice for me?

Regards
Tobias


[cid:image003.jpg@01D66747.4082C820]

Reply via email to