[sr-dev] crash during TLS tests

[Klaus Darilion]

Andrei Pelinescu-Onciul schrieb:
> On Jan 21, 2010 at 19:13, Klaus Darilion <klaus.mailinglists at pernau.at> wrote:
>> Hi!
>>
>> Today kamailio 3.0 crashed during TLS tests. Unfortunately the backtrace 
>> does not say much:
>>
>> # gdb kamailio /tmp/core.kamailio.sig11.24868
>> ...
>> Core was generated by `/usr/sbin/kamailio -P 
>> /var/run/kamailio/kamailio.pid -m 64 -u root -g root -f /'.
>> Program terminated with signal 11, Segmentation fault.
>> [New process 24868]
>> #0  0x0814e5f0 in fm_malloc (qm=0xb36d0000, size=<value optimized out>) 
>> at mem/f_malloc.c:194
>> 194                             if (frag->size <= (*f)->size) break;
>> (gdb) bt
>> #0  0x0814e5f0 in fm_malloc (qm=0xb36d0000, size=<value optimized out>) 
>> at mem/f_malloc.c:194
>> #1  0xb787a2da in ser_malloc (size=21848) at ../../mem/shm_mem.h:256
>> #2  0xb7c9c4ce in ?? () from /usr/lib/i686/cmov/libcrypto.so.0.9.8
>> #3  0x00005558 in ?? ()
>> #4  0xb7d97124 in ?? () from /usr/lib/i686/cmov/libcrypto.so.0.9.8
>> #5  0xbfdd7828 in ?? ()
>> #6  0xb7c9cb4f in CRYPTO_malloc () from 
>> /usr/lib/i686/cmov/libcrypto.so.0.9.8
>> Backtrace stopped: frame did not save the PC
> 
> Could you compile with malloc debugging?

I recompiled with malloc debugging, but since then the crash did not 
happened again.

> It looks like a messed memory fragment, but it doesn't have to be the
> TLS code, it might be some other module you have loaded.
> 
> If you manage to reproduce it, try to reduce the config to a minimum,
> just in case it's not really TLS related.
> Trying another newer version of openssl would also help (in case the bug
> is in openssl).

Ok. Thanks. I wait for the crash to happen again.

regards
klaus