No, the problem is definitely in your code, and TSN was trying to tell you exactly where. You are dealing with a very basic C problem involving pointers. Let me rephrase that: Your crash is not caused by anything that has to do with the Acrobat SDK. Do yourself a favor and get a good C/C++ resource and re-read the chapter about pointers.
Your application is no longer crashing because something in the memory layout of your computer has changed (e.g. you started a different application, you rebooted, you modified your code so that things end up in different locations in your memory, ...). Now your code is overwriting some data in your application. This is what the alternative to crashing is: You end up with corrupt data, and you don't even know that it's happening. Something will go horribly wrong somewhere in your program. That's why a crash is better than the alternative.