On Dec 17, 2014, at 8:06 AM, T@Run..............! Polisetty <[hidden email]> wrote:
I am reporting one coredump when using openssl library
Can anyone have some idea on it.
hread 1 (Thread 28457):
#0 0x00007f1871bb61b5 in raise () from /lib/libc.so.6
#1 0x00007f1871bb8fc0 in abort () from /lib/libc.so.6
#2 0x00007f1871bec5bb in ?? () from /lib/libc.so.6
#3 0x00007f1871bf5e16 in ?? () from /lib/libc.so.6
#4 0x00007f1871bfab8c in free () from /lib/libc.so.6
#5 0x00007f187721c6b8 in CRYPTO_realloc_clean ()
#6 0x00007f187727e8c5 in BUF_MEM_grow_clean ()
#7 0x00007f187727fde7 in mem_write () from
#8 0x00007f187727eec9 in BIO_write () from
Offsets alone are pretty much meaningless, especially since we don’t know (a) what architecture this is, (b) what version this is, (c) if this is a debug or optimized build, (d) what the line numbers are, (e) what platform you’re running this one, (f) if any patches have been applied, (g) what you were doing at the time that the coredump happened, (h) what data can reliably reproduce this…
At a minimum, please provide (d) and (h).
If you’re using a production build in a fairly mainstream distro, there should be a package containing debug symbols that you can install corresponding to the library packaging (usually suffixed -dbg, -debug, or -devel).