-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Core / Service]: Fixed crash that occured when communicating with eCAL 5.12 services #1579
Conversation
…AL 5.12 services The crash occured when a v0 client connected to a service server.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't quite understand why start() already calls user defined callbacks, and how that solves the problem. Is start()
called by the user themselves? Maybe a flow diagram would help me understand. otherwise looks good 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clang-tidy made some suggestions
@@ -1605,6 +1605,151 @@ TEST(ecal_service, Callback_SerializedServiceCallbacks) // NOLINT | |||
} | |||
#endif | |||
|
|||
#if 1 | |||
// Call different eCAL Service API functions from within the callbacks | |||
TEST(ecal_service, Callback_ApiCallsFromCallbacks) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
warning: all parameters should be named in a function [readability-named-parameter]
TEST(ecal_service, Callback_ApiCallsFromCallbacks) | |
TEST(ecal_service /*unused*/, Callback_ApiCallsFromCallbacks /*unused*/) |
ServerSessionV0::Start() is called by the factory create. As the buggy v0 protocol completely lacks any connection establishment, it immediately assumes that it is connected and therefore calls the EventCallback with a connected event. Before, it did that in the same thread. Now it does that in the io_context thread. v1 never had that issue, as the EventCallback is called after the connection has been established. Thus, the event callback has always been called from the io_context thread. |
…AL 5.12 services (#1579) The crash occured when a v0 client connected to a service server.
…AL 5.12 services (#1579) The crash occured when a v0 client connected to a service server.
Description
The crash occured when a v0 client connected to a service server.
Related issues