Support Board

Date/Time: Sun, 05 May 2024 00:24:25 +0000

Post From: Exception in Custom ACSIL study

[2021-05-02 14:41:32] Link To Thread - Link To Post [Go To First Post]
jmt816 - Posts: 45
Thanks Brad. I guess I wasn't as clear in my post as I had thought. That exception message is only seen in the immediate window when doing interactive debugging. It does NOT trigger a breakpoint in my code, or stop executing (unlike certain other exceptions), so i am unable to see the call stack to be able to identify what in my code is potentially causing that exception to be thrown from Sierra's KernelBase.dll. Because it is not triggering any break during execution, and I see it flying be in the immediate window even if my study is not executing any code, is what has me scratching my head. This exception is only appearing in the immediate window of Visual Studio when I have my code attached for debugging. It does NOT appear in the Sierra Message log (where exceptions usually appear). Was hoping that Sierra Engineering might be able to identify what function is being called in that dll, to see what, if any, part of my code is causing that.