[sr-dev] [tracker] Comment added: Out of memory when a request is sent to itself

[sip-router]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#372 - Out of memory when a request is sent to itself
User who did this - Konstantin (Konstantin)

----------
We investigated this issue in the context of the bigger problem.

We use several custom modules and we met an issue which causes Kamailio server crash.
In all cases we can see that the shared memory is corrupted somehow.

For example,

//Program terminated with signal 11, Segmentation fault.
#0  0x08176264 in fm_malloc ()
(gdb) bt
#0  0x08176264 in fm_malloc ()
#1  0x001a43e2 in shm_malloc (_dom=0x390cdf30, _aor=0x1b9aa4, _contact=0xbfc49408, _ci=0x1b9b20) at ../../mem/shm_mem.h:256
#2  shm_str_dup (_dom=0x390cdf30, _aor=0x1b9aa4, _contact=0xbfc49408, _ci=0x1b9b20) at ../../ut.h:700
#3  new_ucontact (_dom=0x390cdf30, _aor=0x1b9aa4, _contact=0xbfc49408, _ci=0x1b9b20) at ucontact.c:206
#4  0x001b2cd6 in mem_insert_ucontact (_r=0x1b9aa0, _c=0xbfc49408, _ci=0x1b9b20) at urecord.//c:156

Could you recommend how to analyze this problem or 
tools how to analyze core dumps to identify the place where the shared memory was corrupted?
May be there is a way or tool to investigate the shared memory content and its integrity 
to find out the place where control structures were broken?

Thank you in advance.
----------

More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=372#comment1179

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.