If it's getting a signal of SIGBUS or SIGSEGV, or a crash code of
0xc0000005 in Windows, the ssl_connection's internal structures are
being corrupted or (more likely) free()'d improperly. What version of
OpenSSL (0.9.8... what letter revision?), where did you get it? (for
the Windows version), and what are the error diagnostics that you're
getting on Windows?
(Since it's hanging on write(), you're using non-blocking I/O, and the
TCP stack hasn't determined that the peer isn't answering yet. This
shouldn't cause a crash, but it could cause a hang.)
-Kyle H
On Tue, Dec 15, 2009 at 1:02 PM, Josselin Jacquard
<josselin.jacqu...@gmail.com> wrote:
> Hi,
> When I'm connecting to a peer who crashes, I try to close the connection
> with :
>
> if (ssl_connection != NULL)
>
> {
>
> SSL_shutdown(ssl_connection);
> }
>
> It crashes on windows, and on linux, with a debugger attached, the program
> freezes with this call stack :
>
> 0 write /lib/libpthread.so.0 0
> 1 sock_write /usr/lib/libcrypto.so.0.9.8 0
> 2 BIO_write /usr/lib/libcrypto.so.0.9.8 0
> 3 ssl3_write_pending /usr/lib/libssl.so.0.9.8 0
> 4 ssl3_dispatch_alert /usr/lib/libssl.so.0.9.8 0
> 5 ssl3_shutdown /usr/lib/libssl.so.0.9.8 0
>
>
> Does someone have an Idea about this ?
>
> Thanks in advance
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
