[Kamailio-Devel] Resp.: [Kamailio-Users] Help to create in core

[Henning Westerholt]

On Monday 15 September 2008, Marcio wrote:
> Version used = openser 1.3.0-no-tls;

Hi Marcio,

ok, understand.

> thx by advices, but i'm newbie too in 'c'.....so i did debug setting
> debug level 4 and find it:
> Sep  5 17:30:07 notehome openser[29088]:
> DBG:mysql:db_mysql_new_connection: server version is
> 5.0.38-Ubuntu_0ubuntu1.4-log
> Sep  5 17:30:08 notehome openser[29084]: INFO:core:handle_sigs: child
> process 29088 exited by a signal 11

You need to investigate what happens between this call in the db API, and the 
signal 11 that causes the crash.

> The proxy openser, when receive a request "register"...the main.c in
> "switch(sig_flag) / case SIGCHLD / line "else if
> (WIFSIGNALED(chld_status))....LM_INFO(child process chld exited by
> signal...") how seen above....after to pass
> [..]
> at this point the control returns to "main.c" and kill the pid ....
>               "switch(sig_flag) / case SIGCHLD / line "else if
>     (WIFSIGNALED(chld_status))....LM_INFO(child process chld exited by
> signal...")
> .....
 
I think the problem is more in your module, then in the core. Have you add 
some log statements, e.g. 'LM_ERR("foobar");' to your module function to see 
where exactly it crashed? Then you could follow the execution of this 
function in the log files. 

> Actually I think I lost .....when i run into shell(linux) #
> openser.....he is executing no probs, but when receive um request
> "register" i routed to route[2] and test with "if (is_from_trusted() )
> {.........} then he dead...with log above....

As i said, just add some custom log statements to this function, and do 
the "register", follow the execution of the function and see where it crashes 
exactly. 

Cheers,

Henning