I have a client that connects to a the UACPP sample server. I am trying to start 15 sessions to the server and read a number of nodes off of it. For some reason the UaClient_Session_BeginRead() function crashes from time to time. The data going into the function is the same but for whatever reason after a certain number of successful calls to the function, it crashes. Is this a known issue or do you have any information that may be helpful in diagnosing it?
Thank you,
Andres
Read call breaking
Moderator: uasdkc
- Support Team
- Hero Member
- Posts: 3078
- Joined: 18 Mar 2011, 15:09
Re: Read call breaking
Hello andres,
the AnsiC Client SDK doesn't have any known issues when simply reading values from a server. This scenario has been tested very well. For diagnosing the problem, you might find memory tracing tools like valgrind, GCC's or clang's address sanitizer (-fno-omit-frame-pointer -fsanitize=address) or MemoryValidator helpful. Also, enabling the trace on the highest level can give you hints about where the problem is.
Best regards
Unified Automation Support Team
the AnsiC Client SDK doesn't have any known issues when simply reading values from a server. This scenario has been tested very well. For diagnosing the problem, you might find memory tracing tools like valgrind, GCC's or clang's address sanitizer (-fno-omit-frame-pointer -fsanitize=address) or MemoryValidator helpful. Also, enabling the trace on the highest level can give you hints about where the problem is.
Best regards
Unified Automation Support Team