<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 05/15/2013 12:14 PM,
Daniel-Constantin Mierla wrote:<br>
</div>
<blockquote cite="mid:51932EDF.7010001@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hello,<br>
<br>
<div class="moz-cite-prefix">On 5/15/13 6:43 AM, kiran bhosale
wrote:<br>
</div>
<blockquote cite="mid:5193125D.9050103@synteltelecom.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hi<br>
we have developed the custom module where in we have created
shared memory area which is not used by any other module or
process and we locked it using locks as recommended. but
because of locks the kamailio is getting crashed every now
and then . is it really important to protect the shared
memory area with locks. if yes then how to avoid the crash
?? <br>
<br>
so to locate the crash we built kamailio wit h MM_DBG , and
other GCC debug flags . but we are getting error "<i>No
symbol table info available</i>" . how to locate the
bugs. the kamailio is built wit h 1 MB of shared memory on
MIPS based VOIP gateway which is having * MB of flash and
16 MB or memory (RAM) .<br>
</blockquote>
set ulimit-c unlimited in order to get a core file, then use gdb
to get the backtrace from the core. It will show where the crash
happened.<br>
<br>
Protection to shared memory is needed only when there is potential
concurrent access.<br>
<br>
Cheers,<br>
Daniel<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://twitter.com/#%21/miconda">http://twitter.com/#!/miconda</a> - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
* <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://asipto.com/u/katu">http://asipto.com/u/katu</a> *</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
we did that as well but we get these backtrace "No symbol
table info available " errors when we tried to debug the core
file. our requirement is simple . we have not used any DB for
storage of users. instead we have implemented local structures
for them. but we want to delete these users after the "expires"
becomes zero. but when we tried to delete them using kamailio
timer or "register_timer" function . it is in no way accessing
these local structures . which is why we used shared memory.
but it is leading to crash . even we tried to unstrip the
kamailio and ld.so . but that also didn't give exact location
of crash. our kamailio footprint is around 1.7 MB with logs
and 900 KB without logs. <br>
<br>
<br>
1) is there any possibilty of other process/module corrupting
our data it being a shared memroy ?? <br>
2) the modules we used are tm.so , sl.so registrar.so textops.so,
auth.so auth_db.so and syntel.so(our module). <br>
3) when run with 10 instances of SIPP it crashed after two
hours.<br>
is it mandatory to use shared memory for users to be deleted
periodically. isnt there any workaround to access local variables
from kamailio timers. <br>
i can share our code with you .<br>
<br>
please help <br>
<br>
<br>
</body>
</html>