Re: memory corruption after libssl is unloaded from memory

2010-08-16 Thread Ladar Levison
On 8/16/2010 8:11 AM, Jan Pechanec wrote: On Fri, 13 Aug 2010, Ladar Levison wrote: I was able to dynamically load OpenSSL, initialize it, unload it, and then reload it back up again using your example along with some of my cleanup code. Since I don't know your specific use case, I don't know

Re: memory corruption after libssl is unloaded from memory

2010-08-16 Thread Jan Pechanec
On Fri, 13 Aug 2010, Ladar Levison wrote: > I was able to dynamically load OpenSSL, initialize it, unload it, and then > reload it back up again using your example along with some of my cleanup code. > Since I don't know your specific use case, I don't know if something like this > will work for y

Re: memory corruption after libssl is unloaded from memory

2010-08-16 Thread Jan Pechanec
On Fri, 13 Aug 2010, Darryl Miles wrote: > > While it is possible to make a Valgrind clean (as in memory leaks) executable, > that loads OpenSSL DSO/DLLs exactly once during the executable lifetime. > > I'm not sure it has ever been a feasible goal to make OpenSSL DSO/DLLs able to > be unloaded (w