Fixed years ago by Richard L.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Autom
I stumbled across the same crashes that Philip did in crypto/err/err.c
when used in a multithreaded application. I initially observed the
problem in 0.9.7b under Linux, but found it was much easier to
reproduce when running under the debugger of MSVC 6.0. In particular,
I would often see a cras
I agree entirely that a reference counter is the way to go. However, the
complexity is much higher, and *for my purposes* the solution that I
described works adequately.
Thanks for doing a proper fix!
Philip
Richard Levitte via RT wrote:
>It seems to me that adding a reference counter is a b
OK, just implemented and committed. Please try tomorrow's snapshot.
I'm not releasing this ticket yet, as I suspect there may be discussions
about this change...
[levitte - Sat Sep 27 22:19:53 2003]:
> It seems to me that adding a reference counter is a bit better. This
> means that we need t
It seems to me that adding a reference counter is a bit better. This
means that we need to have one extra function (and callback) to release
a pointer (and thereby decreas the reference count).
I'm experimenting with that approach as I write, and I'm going to
release soon unless someone sees a p
I get a crash in the lhash code in Openssl 0.9.7a. The troublesome case
is when it is called from err/err.c in a multithreaded environment.
The root cause *may* be that the hash is destroyed by
int_thread_del_item while (say) int_thread_get has a copy of the
pointer. The locking does not seem
