https://bugs.openldap.org/show_bug.cgi?id=9098
--- Comment #17 from nivanova@symas.com nivanova@symas.com --- Hello again, We have tried to reproduce the issue, but so far without success - with or without timeouts, and running with helgrind did not show any relevant errors. We will keep trying, but in the mean time: The trace you provided shows something curious. We have the assertion error in Thread 1, and at the same time, we have Thread 8 performing ldap_sasl_bind on the same mc. It could be on a different candidate, in which case this would be irrelevant, but to make sure - if you still have the core and are able to open it, can you give us the following: In thread 1 at #4 , the value of i and of candidates[i] In thread 8 at #9, the value of candidate and candidates[candidate]
It also seems something strange has happened to the data, entry values are different from the current, and the pointers seem off...
We may need to add a few additional log messages to check the flow and data state since we can't debug. Given that you also can't reproduce it in a test environment, how feasible would be to deploy a build in production that has only log messages added?