We are using openssl-32bit-0.9.8a-18.26 on SLES 10.2 (x86_64). This problem is only occurring on a very small percentage of our installs, and is not readily repeatable, but is always results in the same back trace.
Program terminated with signal 11, Segmentation fault. #0 0xb7bf54e3 in ssl3_read_n () from /usr/lib/libssl.so.0.9.8 (gdb) bt #0 0xb7bf54e3 in ssl3_read_n () from /usr/lib/libssl.so.0.9.8 #1 0x00000000 in ?? () (gdb) quit I'm digging into this issue more and can provide more information when I get it as far as what is calling ssl_read_n and what is being passed in. I have two questions right now though: 1) Are there any known issues as to why ssl3_read_n would cause a segmentation fault? 2) Is there any know reason why the call trace would be truncated? There is nothing past #1) and the other threads have clean call traces. Dwight Schauer dscha...@buchanan.com ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
