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
Prevent no unique connection bridge name #446
Comments
Hello,
by:
What do you think about it ? Correction ;-) ? C-U |
ralight
added a commit
that referenced
this issue
May 12, 2017
Thanks to Tifaifai Maupiti. Bug: #446
Thanks for reporting this, I see the crash as well. I've fixed it in a different way by not allowing duplicates. |
Tifaifai
pushed a commit
to Tifaifai/mosquitto
that referenced
this issue
May 15, 2017
Thanks to Tifaifai Maupiti. Bug: eclipse#446
Tifaifai
pushed a commit
to Tifaifai/mosquitto
that referenced
this issue
May 15, 2017
Thanks to Tifaifai Maupiti. Bug: eclipse#446
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
In case of no unique connection bridge name in mosquitto.conf, mosquitto crash with a segmentation fault.
example:
We know that it's not a good practice (same name for connection) but the reaction of mosquitto can be better.
A first bad solution is prevent this bug with rename the bridge by default
in
conf.c
, line 928replace by:
Have you a better solution for prevent segmentation fault and crash ? because we don't understand this problem (no use
bridges[i]->name
after).THX
The text was updated successfully, but these errors were encountered: