General hint:
seg-faults in malloc(), free(), realloc() etc. are usually caused by earlier
corruption of the heap. Looking at the stack at the time of crash is
rarely successful.
A better hint is to link to a special debug variant of malloc(), which is
specifically designed to report the exact p
Hi,
I am observing a seg-fault with following back-trace-
#0 0x089277fe in _int_malloc ()
#1 0x08926a72 in malloc ()
#2 0x087df811 in default_malloc_ex (num=4, file=0x89eda40 "bn_lib.c",
line=336) at mem.c:79
#3 0x087dfe30 in CRYPTO_malloc (num=4, file=0x89eda40 "bn_lib.c",
line=336) at mem.
