When I compile the simple email sample program.
About 1 out of 3 times, the following code dies trying to read x0000 or x0005:
That's about as simple as a create possible. Any idea why?
I'm sorry to say that I have not been able to reproduce this problem. Given that the Chilkat API is 10+ years old, and used by tens of thousands of customers, it is possible, given that a new application written in C++ could've corrupted memory (or the stack) such that the corruption is not noticed until some later point in time when heap or stack activity trips over the landmine that was previously set..