Access violation problem
Posted: Monday 11 July, 2011 - 09:17
Hi,
So last week when I finished up for the week I was happy that I got my model working the way I wanted it to. However, today when I got back to it, I always get an "Access violation in module 'ED.exe'". This is the EXACTLY same model that worked just fine last week.
To make things worse, the access violation does not happen when I run the model in debug mode and only use step into. The model just works ok when I do this.
So how really am I supposed to debug this? All I get is an access violation popup (that I'm unable to close unless I'm running the debugger, spam enter key and spam-click the stop-button of the debugger, but that's a whole another matter) that tells me nothing about the problem. And how is it even possible that while nothing has changed, the model goes from fully working to completely broken?
So last week when I finished up for the week I was happy that I got my model working the way I wanted it to. However, today when I got back to it, I always get an "Access violation in module 'ED.exe'". This is the EXACTLY same model that worked just fine last week.
To make things worse, the access violation does not happen when I run the model in debug mode and only use step into. The model just works ok when I do this.
So how really am I supposed to debug this? All I get is an access violation popup (that I'm unable to close unless I'm running the debugger, spam enter key and spam-click the stop-button of the debugger, but that's a whole another matter) that tells me nothing about the problem. And how is it even possible that while nothing has changed, the model goes from fully working to completely broken?