-
Notifications
You must be signed in to change notification settings - Fork 392
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
Roudi message queue thread startup #171
Labels
bug
Something isn't working
Comments
dkroenke
pushed a commit
to dkroenke/iceoryx
that referenced
this issue
Jul 3, 2020
Signed-off-by: Kroenke Dietrich (CC-AD/ESW1) <[email protected]>
dkroenke
pushed a commit
to dkroenke/iceoryx
that referenced
this issue
Jul 3, 2020
… initialized after destroy or move Signed-off-by: Kroenke Dietrich (CC-AD/ESW1) <[email protected]>
dkroenke
added a commit
to dkroenke/iceoryx
that referenced
this issue
Jul 6, 2020
Signed-off-by: Kroenke Dietrich (CC-AD/ESW1) <[email protected]>
dkroenke
added a commit
to dkroenke/iceoryx
that referenced
this issue
Jul 7, 2020
Signed-off-by: Kroenke Dietrich (CC-AD/ESW1) <[email protected]>
dkroenke
added a commit
that referenced
this issue
Jul 9, 2020
…read-startup iox-#171 added option to defer mq thread startup
dkroenke
pushed a commit
to dkroenke/iceoryx
that referenced
this issue
Jul 29, 2020
Signed-off-by: Kroenke Dietrich (CC-AD/ESW1) <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When starting RouDi immediatlly after the applications , it can happen that the Message Queue in RouDi is not yet ready and the applications already start to send messages. This could lead to a segmentation fault in RouDi.
To prevent that we let the Message Thread start only when the RouDi has started complety.
The text was updated successfully, but these errors were encountered: