Hi all,
I am a HP employee and we use OpenSSL in one of our applications by
creating a static library libssl.a and linking against it. The
application runs on various platforms like Windows, Linux, HP-UX,
OpenVMS and etc.
In one of the customer setup running HP-UX 11.31 ia64, the application
crashes. On debugging the core with gdb, the backtrace points to some
issue with OpenSSL library. The version of the library we are using is
very old - 0.9.8. Can anyone tell me anything that will be useful in
debugging the issue by looking at the backtrace below? The stack
backtrace is not complete but stack frames from 6 onwards belong to
the application and not to openssl. So I have trimmed the stack
frames.
<snip>
# gdb ./SSSU ./core
HP gdb 6.1 for HP Itanium (32 or 64 bit) and target HP-UX 11iv2 and 11iv3.
Copyright 1986 - 2009 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 6.1 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..
Core was generated by `SSSU'.
Program terminated with signal 11, Segmentation fault.
SEGV_ACCERR - Invalid Permissions for object
#0 0x60000000d4f016a0:0 in ssl3_read_n () at s3_pkt.c:206
206 s3_pkt.c: No such file or directory.
in s3_pkt.c
(gdb) bt
#0 0x60000000d4f016a0:0 in ssl3_read_n () at s3_pkt.c:206
#1 0x60000000d4f019b0:0 in ssl3_get_record () at s3_pkt.c:264
#2 0x60000000d4f04680:0 in ssl3_read_bytes () at s3_pkt.c:849
#3 0x60000000d4efd930:0 in ssl3_read_internal () at s3_lib.c:1737
#4 0x60000000d4efae80:0 in ssl3_read () at s3_lib.c:1757
#5 0x60000000d4f17f30:0 in SSL_read () at ssl_lib.c:846
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile libccb.a(secsocket_ossl.o).
If NOT specified will behave as a non -g compiled binary.
#6 0x4600d50:0 in ccb2::SecureSocket::readAvailable(unsigned
char*,unsigned int,unsigned int&)+0xf0 ()
#7 0x4602000:0 in ccb2::SecureSocket::readBlock(unsigned char*,unsigned int)
+0x130 ()
</snip>
If the issue is with the old version of openssl and is possibly fixed
with the newer versions, is the upgrade path straightforward? Is the
API compatibility maintained? Would love to hear thoughts on this.
Thanks & Regards,
Guruprasad
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
