Re: crash when using LDAP_OPT_RECONNECT

On Aug 16, 11:34 am, Anton Bobrov <[email protected]> wrote:
> its most probably because you have other pending requests that catch
> that connection dead after reconnect handler. what happens if that
> connection goes bad on the last request ?

Then the refcount will be only 1 since no requests refer to it, and
the connection will be cleaned up in the simple_bindifnot_s even
without force, since refcount drops to zero.

My assumption is that all request structures must eventually be
cleaned up, or else there is a big leak there, and when a request is
cleaned up, the corresponding connection always has its refcount
decremented.

In short, ISTM that the refcount mechanism works, and it's not clear
to me how the simple_bindifnot_s workflow should be different and use
force == 1.  Don't the same considerations apply there to any code
that needs to handle normal connection cleanup, or dead connection
cleanup?