Tracing Source of Error 55555

Hi, have started working in simulation and am receiving the below error.

There is no backtrace available, and I have not been the one working on Module01 so I’m not sure where to begin.

What tools are available in a situation like this? I feel I’ve been careful to have my global changes not effect anything.

My next step was to reverse my changes to see if the last copy of the software was working in the first place.

Hi Adam,

That error is raised by the IEC Check library. The purpose of this library is to catch programming mistakes before they cause memory issues.

Specifically, the CheckBounds function flags if an array is accessed using an invalid index (meaning, one that is higher or lower than its valid range). I would recommend looking through the Module01 task for any lines of code that access arrays to see where this invalid index could be. The debugger is a helpful tool in this case!

Of course, you can remove the IEC Check library from your project to prevent this error. However, I’d recommend finding the issue anyway because it could cause memory issues later on.

You can also check out this post from a while ago: Troubleshooting Page Faults - Share Info & Ideas - B&R Community. Towards the end of the post, there is a link to a different version of this library called the AdvIecCheck library. This is an unofficial version of IEC Check which has the same functions, but slightly modified implementation. Specifically, it forces a pagefault after finding an error in a way that gives you backtrace information to the exact line of code that caused the issue.

3 Likes