On Sun, Mar 20, 2005, Chris Brown wrote:
> I didn't get any replies to this when I sent it last week. Am I on the
> wrong list for this sort of query?
>
No, just haven't had time to look at it yet.
>
>
> I've manage to diagnose this down further to a snippet of code inside
> ERR_STATE *ERR_
I didn't get any replies to this when I sent it last week. Am I on the
wrong list for this sort of query?
Chris...
=== original message ===
I've manage to diagnose this down further to a snippet of code inside
ERR_STATE *ERR_get_state(void)
on roughly line 1022 of crypot/err/err.c of the 0.9.7-f
I've manage to diagnose this down further to a snippet of code inside
ERR_STATE *ERR_get_state(void)
on roughly line 1022 of crypot/err/err.c of the 0.9.7-f-snapshot
(from the 11th):
if (ERRFN(thread_get_item)(ret) != ret)
{
cmb_ssl_dbg( "crypto thread_get_item failed" );
ERR_STATE_free(ret); /* co
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
>
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, f
On Sat, Mar 12, 2005, cmb wrote:
> I'm having some difficulty diagnosing a double free that appears to be
> within the openssl library. I assume I'm feeding it bad data, but I'm
> having a great deal of difficulty bringing openssl under the gdb microscope.
>
> This is what I've been able to de
