Alright, a little more information. I took the example cli/serv ssl source from the openssl distribution and messed it up so that SSL_read would segfault in the serv executable.
Compiled and ran the resulting pair and got a core file and examined it. On an up to date Arch linux install the back trace was clean and I could tell where the problem was. On an up to date OpenSUSE 10.3 install the back trace was clean and I could tell where the problem was. On a SLES 10.2 install however, the segfault in SSL_read function function trashed the stack and made the back trace useless. All examples were compiled on their respective installs. On SLES I tried both openssl-0.9.8h-30.11 (rebuilt from SRC RPMs for SLES) and openssl-0.9.8a-18.26. Same behavior for both. I can mess up other code on apps I run on SLES and get meaningful back traces from the resulting coredumps. The development team I'm on does a lot of application development for SLES, and most of the time coredumps provide meaningful back traces. However, they never seem to with SSL functions in our experience. Any insight into this issue would be very much appreciated. -----Original Message----- From: Dwight Schauer Sent: Thursday, October 01, 2009 11:07 To: 'openssl-users@openssl.org' Subject: Segmentation fault in ssl3_read_n and shortened stack strace 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 ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
