Login Page - Create Account

Support Board


Date/Time: Thu, 25 Apr 2024 14:09:43 +0000



[Programming Help] - Exception in Custom ACSIL study

View Count: 666

[2021-05-01 15:46:39]
jmt816 - Posts: 45
In the course of developing a custom study, somewhere along the line I started getting an exception being thrown from Sierra. It does not appear to cause any issues, but clearly something I did is causing it. I know that you do not provide programming help, and am not looking for any. Am just wondering if it is possible for you to identify this exception so that I can then track its source?
This is the message:
"Exception thrown at 0x00007FF81DE34B59 (KernelBase.dll) in SierraChart_64.exe: 0x0EEDFADE (parameters: 0x000000002711D2AE, 0x000000000F60DBA0, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)."

Thanks in advance
[2021-05-01 21:36:03]
bradh - Posts: 854
Have you tried using debug mode with the study? You should see more information about the exception in Visual Studio when it happens. If the exception is thrown immediately after loading the study, then attach the debugger before adding the study. When I get them, they are usually due to a divide by zero error or an uninitialized variable.

Step-By-Step ACSIL Debugging
[2021-05-02 14:41:32]
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.
[2021-05-03 03:44:29]
ondafringe - Posts: 248
This individual had a similar issue, unrelated to Sierra Chart. Look at how he tracked down the problem and maybe it will give you some ideas.

https://stackoverflow.com/questions/62267856/kernelbase-dll-exception-code-0x0eedfade-but-no-crash-when-visual-studio-is-no
[2021-05-06 17:39:16]
jmt816 - Posts: 45
Thanks for that suggestion! I mistakenly assumed that it was coming from Sierra code. That article helped me find it, and see that it was nothing to do with MY code at all, but coming from a vendor's custom study.
[2021-05-07 02:20:40]
ondafringe - Posts: 248
Great! Glad you were able to track it down. :)

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account