On Mon, Mar 14, 2005, cmb wrote:

> Thank you, duh, turning on debug for config cleared up all my stack 
> trace problems.
> 
> Here is the excerpt of a stack trace that is double freeing:
> 
> #11 0x081a39db in CRYPTO_free (str=0x0) at mem.c:378
> #12 0x081b1fa6 in ERR_get_state () at err.c:605
> #13 0x081b2023 in get_error_values (inc=1, top=0, file=0x0, line=0x0,
>     data=0x0, flags=0x0) at err.c:748
> #14 0x081b22d9 in ERR_get_error () at err.c:708
> 
> Note that this is different than the one I reported earlier.  I think 
> that both code paths result in this problem, and I'm still not sure it's 
> not an error in my code.
> 
> I'm still doing diagnostics, but my schedule is frenetic, so it might 
> take a while.  If anyone has any thoughts on what might be going on, or 
> a clue as to what to look at, it would be appreciated.
> 

All I can suggest at this stage is to be sure the locking callbacks work
including the thread ID callback if its needed.

--
Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage
OpenSSL project core developer and freelance consultant.
Funding needed! Details on homepage.
Homepage: http://www.drh-consultancy.demon.co.uk
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to