win32 build and freeing pointers

Tobias.Wolf at Tobias.Wolf at
Fri Jul 31 12:31:18 UTC 2020

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?


[cid:image003.jpg at 01D66747.4082C820]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 69203 bytes
Desc: image003.jpg
URL: <>

More information about the openssl-users mailing list