Hello,

On 5/15/13 6:43 AM, kiran bhosale wrote:

Hi
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 ??

so to locate the crash we built kamailio wit h MM_DBG , and other GCC debug flags . but we are getting error "No symbol table info available" . 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) .

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.

Protection to shared memory is needed only when there is potential concurrent access.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
  * http://asipto.com/u/katu *