Sounds like the pointer is *pointing to* memory containing 0x...
i.e. this is a use-after-free error.
You might consider building your app with Address Sanitizer enabled,
that might find the problem earlier during execution.
- Dan
On Fri, Jul 31, 2020 at 5:32 AM wrote:
> Hi guys,
>
>
>
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 "0X", but we are
