This is what I've been able to determine. My application aborts inside SSL_get_error when my memory debugger detects a double free. I have managed to figure out where my call is being made from, however inspecting the data I'm calling with is proving exceptionally difficult because gdb won't backtrace into the ssl library or beyond it. The stack trace appears to end when it enters the memory debugger library free() call.
If the lack of stack trace is a characteristic of the OpenSSL library, is there a way to turn it off, or if this is because I've done something insane, let me know and I'll look into that deeper.
By the way, I have been able to get a partial stack trace by doing a manual dump of the stack and matching it against the program map, however this is not as user friendly as gdb and I haven't figured out variables on the stack yet. Also, this problem occurs rarely in a multi-threaded program, so it's hard to diagnose fully.
Any thoughts on any of this?
Chris...
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
