Memory Access Violation in release but not Debug
BlitzMax Forums/BlitzMax Beginners Area/Memory Access Violation in release but not Debug
| ||
| EDIT: Damn, wrong title. I meant an unhandled memory exception, not a MAV. I'm writing some extra debug functions to track this down, but if someone could give me some idea of what could cause an Unhandled Memory Exception in Release mode but not in Debug mode, that would be great. I'm using SuperStrict and every part of the program is returning correct values and working beautifully, which is why I find it odd that I suddenly get an error as soon as I turn debug off. |
   |