Daniel-Constantin Mierla writes:
The backtrace is for the main process during shut down, which can be a side effect of the real issue. You should enable core dump per pid to see if you get core files from more than one process, then grab backtraces from all those core files to figure out what was the first reason of the crash.
Sorry, but don't know how to enable core dump per pid. Didn't find any cli option for that.
Is it the last master version or some older one (kamailio -v should print the commit id, if you compiled from sources)?
Just built K from current master and it crashes every time with similar gdb trace when I stop it using 'service sip-proxy stop'.
-- Juha