What is the value of tcp_children on your config? Do you listen on a tcp
socket?
I need also more from gdb:
frame 1
p tcp_children[0]
Daniel
On 20/05/14 17:44, Peter Villeneuve wrote:
Sure. Thanks Daniel.
#0 handle_ser_child (p=0x7f1ec3adc1d8, fd_i=fd_i@entry=-1) at
tcp_main.c:3579
tcpconn = <optimized out>
tmp = <optimized out>
response = {9034836, 2086}
cmd = <optimized out>
bytes = <optimized out>
ret = -1
fd = <optimized out>
flags = <optimized out>
t = <optimized out>
con_lifetime = <optimized out>
nxt_timeout = <optimized out>
__FUNCTION__ = "handle_ser_child"
#1 0x00000000005328da in send2child (tcpconn=0x7f05815ddda8) at
tcp_main.c:3979
i = <optimized out>
min_busy = <optimized out>
idx = 0
wlast = <optimized out>
last = <optimized out>
crt = 1
wfirst = <optimized out>
#2 handle_tcpconn_ev (tcpconn=0x7f05815ddda8, ev=<optimized out>,
ev@entry=1, fd_i=fd_i@entry=-1) at tcp_main.c:4314
empty_q = <optimized out>
bytes = 0
__FUNCTION__ = "handle_tcpconn_ev"
#3 0x000000000053c428 in handle_io (idx=-1, ev=<optimized out>,
fm=<optimized out>) at tcp_main.c:4366
ret = <optimized out>
#4 io_wait_loop_epoll (repeat=repeat@entry=0, t=5, h=0x89dc40) at
io_wait.h:1092
n = 1
r = <optimized out>
fm = 0x7f058b9da368
revents = 1
#5 0x0000000000544577 in tcp_main_loop () at tcp_main.c:4660
si = <optimized out>
r = <optimized out>
__FUNCTION__ = "tcp_main_loop"
#6 0x00000000004821a8 in main_loop () at main.c:1711
i = <optimized out>
pid = <optimized out>
si = 0x0
si_desc =
"\t\000\000\000\005\177\000\000\000\000\034\000\000\000\000\000\001\000\000\000\005\177\000\000\310\311\027\206\005\177",
'\000' <repeats 18 times>,
"pn\233\213\005\177\000\000\002\000\000\000\000\000\000\000\f\b\000\000\000\000\000\000@\333`\000\000\000\000\000\003\000\000\000\377\177\000\000\000!\006\370
\033\340\337\001\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\210ٓ\000\000\000\000\000\200ٓ\000\000\000\000"
nrprocs = <optimized out>
__FUNCTION__ = "main_loop"
#7 0x0000000000420585 in main (argc=<optimized out>, argv=<optimized
out>) at main.c:2533
cfg_stream = <optimized out>
c = <optimized out>
r = <optimized out>
tmp = 0x7fffd40e1f81 ""
tmp_len = -737279072
port = -163754450
proto = -1
options = 0x608ab0
":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:"
ret = -1
seed = 542838069
rfd = 0
---Type <return> to continue, or q <return> to quit---
debug_save = <optimized out>
debug_flag = <optimized out>
dont_fork_cnt = <optimized out>
n_lst = 0x0
p = <optimized out>
__FUNCTION__ = "main"
(gdb) p *p
Cannot access memory at address 0x7f1ec3adc1d8
(gdb)
On Tue, May 20, 2014 at 4:04 PM, Daniel-Constantin Mierla
<miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote:
Hello,
can you get the output of gdb for 'bt full'?
As well as 'p *p'?
Daniel
On 20/05/14 15:59, Peter Villeneuve wrote:
Well I ended up dumping the core and this is
what GDB tells me.
How can tcp_main.c be missing if I installed the deb packages? Weird.
What do people suggest I do from here? Remove the deb packages
and compile directly from git?
Thanks,
Peter
me@myhost:/$ sudo gdb /usr/sbin/kamailio /home/corefiles/core2
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/sbin/kamailio...Reading symbols from
/usr/lib/debug/.build-id/dd/9191ec1e595a90e4844b8ccd1c70b3c92037a1.debug...done.
done.
[New LWP 30988]
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/kamailio -f
/etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.'.
Program terminated with signal 11, Segmentation fault.
#0 handle_ser_child (p=0x7f1ec3adc1d8, fd_i=fd_i@entry=-1) at
tcp_main.c:3579
3579 *tcp_main.c: No such file or directory*.
(gdb) backtrace
#0 handle_ser_child (p=0x7f1ec3adc1d8, fd_i=fd_i@entry=-1) at
tcp_main.c:3579
#1 0x00000000005328da in send2child (tcpconn=0x7f05815ddda8) at
tcp_main.c:3979
#2 handle_tcpconn_ev (tcpconn=0x7f05815ddda8, ev=<optimized
out>, ev@entry=1, fd_i=fd_i@entry=-1) at tcp_main.c:4314
#3 0x000000000053c428 in handle_io (idx=-1, ev=<optimized out>,
fm=<optimized out>) at tcp_main.c:4366
#4 io_wait_loop_epoll (repeat=repeat@entry=0, t=5, h=0x89dc40)
at io_wait.h:1092
#5 0x0000000000544577 in tcp_main_loop () at tcp_main.c:4660
#6 0x00000000004821a8 in main_loop () at main.c:1711
#7 0x0000000000420585 in main (argc=<optimized out>,
argv=<optimized out>) at main.c:2533
(gdb)
On Tue, May 20, 2014 at 11:33 AM, Peter Villeneuve
<petervnv1(a)gmail.com <mailto:petervnv1@gmail.com>> wrote:
Hi,
I posted previously on this issue but never got any replies.
Has anyone had this experience with 4.1?
It seems that as soon as a UAC tries to register, Kamailio
segfaults:
May 20 09:41:00 vmhost /usr/sbin/kamailio[27806]: ALERT:
<core> [main.c:775]: handle_sigs(): child process 27813
exited by a signal 11
May 20 09:41:00 vmhost /usr/sbin/kamailio[27806]: ALERT:
<core> [main.c:778]: handle_sigs(): core was not generated
May 20 09:41:00 vmhost /usr/sbin/kamailio[27806]: INFO:
<core> [main.c:790]: handle_sigs(): INFO: terminating due to
SIGCHLD
May 20 09:41:00 vmhost kernel: [251087.555502]
kamailio[27813]: *segfault at* 7fa5d1d0a1dc ip
0000000000536104 sp 00007fffaade6c20 error 4 in
kamailio[400000+27a000]
May 20 09:41:00 vmhost /usr/sbin/kamailio[27812]: INFO:
<core> [main.c:841]: sig_usr(): INFO: signal 15 received
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org <mailto:sr-dev@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla -http://www.asipto.com
http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda>
-http://www.linkedin.com/in/miconda
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org <mailto:sr-dev@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev