This repository has been archived by the owner on Sep 14, 2019. It is now read-only.
Coredump on dslink connect [1ee7543447122a4b2ca1504bc3da5b5cebca456a] #6
Comments
|
Thanks for the report! We are taking a look at this today and should have a fix very soon. |
akawamura
pushed a commit
that referenced
this issue
Sep 28, 2018
Fixed message order in case receiver delayed acks and all send msgs are overwritten
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using a 2 broker setup with a C-broker being upstream of DGLux internal broker.
Connecting dsash or other dslinks to the broker sometimes kills the C-Broker. This never happens on the first conenct of a dslink, only if reconnecting.
2016-09-07 13:18:43 INFO [handshake] - DSLink 'Shell-GJkDLmgPepFEHGPTiFgDMklzC1-AV1yoVaPv80dtbPI' has connected broker(2060,0x7fff7f974000) malloc: *** error for object 0x7fa3b9f05ef0: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug Abort trap: 6The text was updated successfully, but these errors were encountered: