Hi, I'm adding some details about my problem : When I receive a SSL_ERROR_SYSCALL (mean the connection closed abruptly) when trying to read, I try to close the connection, wich cause a mem fault in sock_write.
Are we supposed to try to close the connection after receiving a SSL_ERROR_SYSCALL ? If true, how can I avoid the sock_write error ? Thanks in advance Joss 2009/12/15 Josselin Jacquard <[email protected]> > 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 >
