Support Board
Date/Time: Tue, 26 Nov 2024 04:40:04 +0000
Unhandled exception caught message in study
View Count: 1797
| [2014-04-03 23:13:50] |
| onnb - Posts: 662 |
|
hi, I am getting an exception I have never seen before in the message log. There is a line of code in the study that if I remove it, the message does not appear. The line of code simply assigns a value to one of the subgraphs in the study. An unhandled exception was caught in c_Chart::WindowProc. Message: 275, wParam: 100, lParam: 0 | 2014-04-03 18:50:08 |
| [2014-04-03 23:40:32] |
| |
|
With the way this is described, it sounds as though there is a memory corruption going on somewhere. It is probably not that one line of code that you have removed.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-04-03 23:57:44] |
| onnb - Posts: 662 |
|
Agreed. None of the studies on the chart are making any kind of dynamic memory allocations btw (at least not that I know of). I'll follow up if I see more. I ran it with a debugger but it didn't break when the exception was thrown. Probably it was caught somewhere within SC.
|
| [2014-04-04 00:25:27] |
| |
|
You need to go to Debug >> Exceptions within the Visual C++ debugger and enable breaking on Win32 exceptions.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: