today when io tried to start a couple of days old sr, it crashed at start like this:
#0 cfg_update_local (no_cbs=0) at cfg/cfg_struct.h:257 257 cfg_child_cb = cfg_child_cb->next; (gdb) where #0 cfg_update_local (no_cbs=0) at cfg/cfg_struct.h:257 #1 0x08086b2f in cleanup (show_status=0) at main.c:519 #2 0x080870d1 in shutdown_children (sig=<value optimized out>, show_status=0) at main.c:648 #3 0x0808b04b in main (argc=Cannot access memory at address 0x0 ) at main.c:2245
the reason may be that the address that sr is supposed to be listening at, does not exist, but no matter what, sr must not crash:
Oct 12 11:47:56 localhost kernel: [ 4371.305724] sip-proxy[7470]: segfault at 1c ip 08085c34 sp bfa62af0 error 4 in sip-proxy[8048000+164000] Oct 12 11:47:56 localhost /usr/sbin/sip-proxy[7470]: INFO: <core> [udp_server.c:217]: INFO: udp_init: SO_RCVBUF is finally 262142 Oct 12 11:47:56 localhost /usr/sbin/sip-proxy[7470]: ERROR: <core> [udp_server.c:388]: ERROR: udp_init: bind(6, 0x8219380, 16) on 192.98.101.10: Cannot assign requested address
-- juha
On Oct 12, 2009 at 11:52, Juha Heinanen jh@tutpro.com wrote:
today when io tried to start a couple of days old sr, it crashed at start like this:
#0 cfg_update_local (no_cbs=0) at cfg/cfg_struct.h:257 257 cfg_child_cb = cfg_child_cb->next; (gdb) where #0 cfg_update_local (no_cbs=0) at cfg/cfg_struct.h:257 #1 0x08086b2f in cleanup (show_status=0) at main.c:519
How old is it? It should be fixed in 29e63735 (Thu Oct 8 00:14:32) and it should have been broken on git only for 1.5 days :-)
Try sr -V and look at the git version (that way you can see exactly what was the top commit), e.g.:
./ser -V version: ser 2.99.99-pre3 (i386/linux) 275899-dirty ^^^^^^ git log -10 275899
Andrei
Andrei Pelinescu-Onciul writes:
Try sr -V and look at the git version (that way you can see exactly what was the top commit), e.g.:
./ser -V version: ser 2.99.99-pre3 (i386/linux) 275899-dirty ^^^^^^ git log -10 275899
andrei,
unfortunately i already built a new version and cannot check what the crashing version was.
-- juha
On Oct 12, 2009 at 21:58, Juha Heinanen jh@tutpro.com wrote:
Andrei Pelinescu-Onciul writes:
Try sr -V and look at the git version (that way you can see exactly what was the top commit), e.g.:
./ser -V version: ser 2.99.99-pre3 (i386/linux) 275899-dirty ^^^^^^ git log -10 275899
andrei,
unfortunately i already built a new version and cannot check what the crashing version was.
Never mind, try the latest sr_3.0 (the last fix was wrong).
Andrei
-
Andrei Pelinescu-Onciul -
jh＠tutpro.com