Tomáš Mráz
Tomáš Mráz
This would need a lot of work to get into mergeable state. In particular it should not be platform specific and I believe it should be an optional feature that...
Marking as inactive to be closed at the end of 3.4 development cycle unless you would be willing to do the necessary improvements mentioned in my comment above.
> @t8m - When you say it should not be platform specific, would it be sufficient to make it an optional feature that is specific to one platform? In that...
> @t8m If I summarize the discussion, if there is a common consolidated wrapper for a relative path, it could be acceptable? Does it have to work on all platforms...
What I see in the backtrace is that ldap is trying to call OpenSSL when OPENSSL_cleanup() was already called. Who called it or how was the call triggered is not...
We need to find out what calls OPENSSL_cleanup() then. If it is explicitly called by an application, then either this call must be removed or ldap must not do things...
The cleanup done in libldap in the fini handle is not about calling OPENSSL_cleanup() but it is calling into OpenSSL. The problem is something else before that does the OPENSSL_cleanup()...
OPENSSL_cleanup() is NOT libctx-specific. It should NOT be called from a library. After it is called, OpenSSL must never be used again (except of any other OPENSSL_cleanup() call). There is...
I have one more thing to add. For the reason that an application might want to call OPENSSL_cleanup() before it terminates to get a clean valgrind output, it is in...
Yeah, or not call OPENSSL_cleanup() from python.