Re: possible SSL_write bug

[Alessandro Pivi - GLOBALcom engineering]

This is what you requested: (gdb) run Starting program: /home/develop/test/bin/sslTest h:127.0.0.1 port:16001 SSL Connection opened start op w: 7 start op w: 7 start op w: 7 start op w: 7 start op w: 7 start op w: 7 start op Program received signal SIGPIPE, Broken pipe. 0x4011f41e in write () from /lib/tls/libc.so.6 (gdb) where #0  0x4011f41e in write () from /lib/tls/libc.so.6 #1  0x4022bcd6 in BIO_CONNECT_free () from /usr/lib/i686/cmov/libcrypto.so.0.9.8 #2  0x40228dd3 in BIO_write () from /usr/lib/i686/cmov/libcrypto.so.0.9.8 #3  0x4003de8e in ssl3_write_pending () from /usr/lib/i686/cmov/libssl.so.0.9.8 #4  0x4003e1a7 in ssl3_do_compress () from /usr/lib/i686/cmov/libssl.so.0.9.8 #5  0x4003e4bf in ssl3_write_bytes () from /usr/lib/i686/cmov/libssl.so.0.9.8 #6  0x4003b892 in ssl3_write () from /usr/lib/i686/cmov/libssl.so.0.9.8 #7  0x4004bfc9 in SSL_write () from /usr/lib/i686/cmov/libssl.so.0.9.8 #8  0x08048bb7 in writeSocketSSL (msg=0x8049319 "hello\r\n", len=37) at sslTest.c:268 #9  0x08048f62 in main () at sslTest.c:308 There is also the output of the program. I think the focus should not be on the call the caused the crash, but on the call before, which returned 7 even if the connection was closed. David Schwartz ha scritto: Sorry for my bad english, it crashes, it doesn't hang. Then compile with '-g' and run 'gdb' on the core dump. Post the output of the 'where' command. DS ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]