Forwarded to openssl-users for public discussion on how to debug
the problem.

Best regards,
        Lutz

----- Forwarded message from zlgodguy <[email protected]> -----

Date: Tue, 10 Mar 2009 17:22:21 +0800 (CST)
From: zlgodguy <[email protected]>
To: [email protected]
Subject: About OpenSSL crashed in 0.9.8g

hi all:
      my OpenSSL version is 0.9.8g. i find a crashed in OpenSSL. but it can not 
reproduced. the backtraces list as blow:
      Reading symbols from /lib64/libz.so.1...(no debugging symbols 
found)...done.
Loaded symbols for /lib64/libz.so.1
Reading symbols from /opt/ah/lib/libitk.so...(no debugging symbols 
found)...done.
Loaded symbols for /opt/ah/lib/libitk.so
Reading symbols from /lib64/libc.so.6...
(no debugging symbols found)...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/libcrypt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib64/libcrypt.so.1
Reading symbols from /lib64/ld.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib64/ld.so.1
Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/libdl.so.2
Core was generated by `/opt/ah/bin/capwap'.
Program terminated with signal 6, Aborted.
#0  0x0000005556ecc13c in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x0000005556ecc13c in raise () from /lib64/libc.so.6
#1  0x0000005556ecd998 in abort () from /lib64/libc.so.6
#2  0x0000005556a27818 in OpenSSLDie () from /opt/ah/lib/libcrypto.so.0.9.8
#3  0x0000005556a27818 in OpenSSLDie () from /opt/ah/lib/libcrypto.so.0.9.8
Previous frame identical to this frame (corrupt stack?)
 
        who can give me the suggestion ?


----- End forwarded message -----
--
Lutz Jaenicke           [email protected]
OpenSSL Project         http://www.openssl.org/~jaenicke/
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [email protected]
Automated List Manager                           [email protected]

Reply via email to