=0x7fff47418bf8) at main.c:2581
cfg_stream = 0x21fb010
c = -1
r = 0
tmp = 0x7fff47419f70 ""
tmp_len = 32767
port = 1195477710
proto = 0
options = 0x6ff8f8
":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:&
De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé : jeudi 17 septembre 2015 11:40
À : Igor Potjevlesch <mailto:igor.potjevle...@gmail.com>
; 'Kamailio (SER) - Users Mailing List'
<mailto:sr-users@lists.sip-router.org>
Objet : Re: [SR-Users] Multiple crashes
1001
>
> __FUNCTION__ = "dlg_clean_run"
>
> *(gdb) p *dlg*
>
> Cannot access memory at address 0xb02030a01201001
>
> (gdb)
>
>
>
> I hope this will help.
>
>
>
> Regards,
>
>
>
> Igor.
>
>
>
>
>
> *De :*Daniel-Constan
tantin Mierla [mailto:mico...@gmail.com]
Envoyé : jeudi 17 septembre 2015 11:40
À : Igor Potjevlesch ; 'Kamailio (SER) - Users
Mailing List'
Objet : Re: [SR-Users] Multiple crashes of Kamailio 4.2.1
Hello,
from the second trace, can you get output for:
frame 0
list
info local
Hello,
from the second trace, can you get output for:
frame 0
list
info locals
p *dlg
Cheers,
Daniel
On 11/09/15 18:23, Igor Potjevlesch wrote:
>
> Hello Daniel,
>
>
>
> From the two crashes occurred today, I got 2 coredump. So I copy/past
> the result from these 4 backtraces:
>
>
>
> No pr
x7fffdbce69b8) at main.c:2578
cfg_stream = 0x1f28010
c = -1
r = 0
tmp = 0x7fffdbce6f70 ""
tmp_len = 0
port = 0
proto = 32767
options = 0x6fcc00
":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A
Well, not many relevant changes were done for quite some time to core
components, so those should be very stable, but it happened that we
discovered bugs even after more than 5 years, because they can be
triggered by corner cases that don't show up.
Then, we get always new modules, those take time
options = 0x6fcc00
> ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:"
>
> ret = -1
>
> seed = 2249241156
>
> rfd = 4
>
> debug_save = 0
>
> debug_flag = 0
>
> dont_fork_cnt = 0
>
>
Is Kamailio getting too complicated? Trying to do everything?
Kind regards,
<>___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
t_fork_cnt = 0
n_lst = 0xc2
p = 0x7fff08877e7e ""
__FUNCTION__ = "main"
Regards,
Igor.
De : Igor Potjevlesch [mailto:igor.potjevle...@gmail.com]
Envoyé : jeudi 10 septembre 2015 16:43
À : mico...@gmail.com; 'Kamailio (SER) - Users Mailing L
\000\000\000h\321)Ez\000\000\000\2
76}p\000\000\000\000"
nrprocs = 8
__FUNCTION__ = "main_loop"
#11 0x004ab8bf in main (argc=7, argv=0x74d8e998) at main.c:2578
cfg_stream = 0x2019010
c = -1
r = 0
tmp = 0x7ffff4d8ff70
Hello,
there are newer releases in branch 4.2, was there any reason to stop at
4.2.3?
Back to the backtrace, this one is from shutdown, happening during the
cleanup, not showing the reason of the crash at runtime, unless there
was a manual shut down triggered at that moment. Do you have another
c
Hello,
We got some others crashes even after updated to 4.2.3.
>From the last one, I got the following into "bt full":
Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio.pid -m
256 -M 64'.
Program terminated with signal 11, Segmentation fault.
#0 0x00617612 in
Hello,
3 crashes occurred today (we never seen crashes on this server before)
during a period of 20 minutes.
I had a look to the coredumps. Here is a quick overview of the first entries
of "bt full":
core.27671 : #0 0x7f5577048d65 in run_trans_callbacks_internal
(cb_lst=0x7f5560abb
14 matches
Mail list logo
