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
_mosquitto_destroy is canceling thread #166
Labels
Milestone
Comments
ralight
added a commit
that referenced
this issue
May 18, 2016
libmosquitto shouldn't cancel threads it didn't create. This change allows us to keep track of whether threads were created by the library or by external code. Thanks to Josip Ćavar. Bug: #166
Yes, I agree. This should be fixed now. Thanks for the report. |
Great, thank you for fixing it this fast! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi again,
So we use our own threads with mosquitto. We are calling
mosquitto_new
from Thread 1 andmosquitto_loop_forever
from Thread 2. Now,mosquitto_new
assignsthread_self()
asthread_id
which is in our case Thread 1 id._mosquitto_destroy
calls thenpthread_cancel
on it so Thread 1 is canceled.We were able to workaround this by moving everything to Thread 2, but I think mosquitto should destroy threads only in case
mosquitto_loop_start
is called which is signal to mosquitto to use its own threads.Does this make sense?
The text was updated successfully, but these errors were encountered: