You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
migrated from Bugzilla #473105
status UNCONFIRMED severity normal in component Mosquitto client library for 1.4
Reported in version 1.3.x on platform All
Assigned to: Roger Light
On 2015-07-20 14:24:18 -0400, Trygve Laugstøl wrote:
The v1.3 and v1.4 constructor both look like this:
If the user does something dumb (like passing in NULL and false for id and clean_session) mosquitto_new will return NULL and set errno to EINVAL. The next call will then execute pthread_mutex_lock(&mosq->callback_mutex); but mosq will be NULL.
I'm not sure what the best way to handle the problem is. Options include throwing an exception, just drop setting the callbacks and have the sub-class/user check errno or have a static method that returns the instance. The last option makes it harder to follow the current pattern of extending mosquittopp.
The text was updated successfully, but these errors were encountered:
migrated from Bugzilla #473105
status UNCONFIRMED severity normal in component Mosquitto client library for 1.4
Reported in version 1.3.x on platform All
Assigned to: Roger Light
On 2015-07-20 14:24:18 -0400, Trygve Laugstøl wrote:
The text was updated successfully, but these errors were encountered: