On 5/15/13 9:06 AM, kiran bhosale wrote:
On 05/15/2013 12:14 PM, Daniel-Constantin Mierla wrote:
[...]
 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.


1) is   there  any possibilty of other  process/module   corrupting our data it being  a shared  memroy ??
2) the modules we  used are  tm.so , sl.so registrar.so  textops.so, auth.so auth_db.so and syntel.so(our module).
3) when  run with  10 instances  of  SIPP it  crashed after  two  hours.
is  it mandatory  to use  shared  memory  for users  to be  deleted  periodically. isnt there  any workaround to access local variables  from kamailio timers.
i can  share  our code  with you .
be sure you compile with debugging symbols, it seems you optimize at the compilation time, because you say you remove the logs as well. For the purpose of troubleshooting, do the test with a version compiled normally.

You need shared memory if you have to work on the same structure from different processes.

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 *