Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 02 May 2024 00:25:09 +0000
Post From: Caught an unhandled exception in AsyncWindowProc for ACSIL Study
| [2015-11-22 04:19:06] |
| |
|
Is this something that you developed?: "Log4Cplus library" "message 1025 and what wParam and iParam points to". 1025 is a message code used for various messages within Sierra Chart. It is nonspecific. For your information, if we saw this error while we were doing debugging, in most cases we would not even bother to check any of these parameters because they are not relevant to the problem. And assuming we did look at the message for more details, we would only look at the 1025 message code parameter which is nonspecific. The additional parameters are totally irrelevant. Also that message can occur for numerous reasons and to us it is very vague as to where exactly it is happening. So the message in and of itself basically tells us very little. Please trust us when you we say that you are going very far off course by putting attention on the details of that message. The only thing you need to know, is that most likely memory is getting corrupted. Memory corruptions can cause totally unrelated problems and problems at a later point in time compared to when the corruption occurred. You really should perform step-by-step debugging. Refer to the documentation for the instructions for that for Visual C++. Usually when an exception occurs in a program and the program is terminated by the operating system and the operating system provides a large amount of details which include the memory address where the exception occurred, the exception code, CPU register values, and numerous other details, none of that other than the exception code is something that we pay attention to because most that information is too low-level to be useful. We may look at the address where the exception occurred in the case of an access violation exception to see if it is very close to zero which indicates the use of a null pointer. 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 Date Time Of Last Edit: 2015-11-22 07:34:55
|