Hi,
> > Core 1
> > ----------
> > (gdb) bt
> > #0 0x4021e76e in pclose () from /lib/libc.so.6
> > #1 0x4021e548 in _IO_proc_close () from /lib/libc.so.6
> > #2 0x400b4772 in CRYPTO_free (str=0x0) at mem.c:380
> > (gdb)
> And if I read that backtrace in the correct direction,
Sorry to interrupt, but no, you didn't read it in the correct
direction. It's pclose being called by _IO_proc_close which in
turn was called by CRYPTO_free...
> _I_ would suspect my own code and since this yaks about a pclose() my
> first question to the team would be: what have we got on pipes in our
> project? And see if you can put some diagnostics around it.
Either that or a completely corrupted stack or heap, in which case
something like valgrind or purify is probably going to be helpful in
finding the _real_ problem.
> And while you're at it, and assuming you're in a multithreaded app,
> check whether the OpenSSL thread lock hooks are done properly, just to
> cover all the bases.
(snipp)
> My bet is some part of your software has gone totally bonkers. With
> OpenSSL being part of the collateral.
Agreed.
Regards,
Stefan
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
