19 Jul
2009
19 Jul
'09
6:08 p.m.
i have never used k dialog module because it is by far the buggies
module that k has. now i ventured to try and, by no surprise, i crashed
sr before a single message went through. looks like it started to play
with db although i had not defined any.
-- juha
(gdb) where
#0 0x00000000 in ?? ()
#1 0xb728bba4 in dlg_connect_db (db_url=0xb72ab574) at dlg_db_handler.c:119
#2 0xb72885e8 in child_init (rank=2) at dialog.c:576
#3 0x080e0f1b in init_mod_child (m=0x8231b20, rank=2) at sr_module.c:808
#4 0x080e0e90 in init_mod_child (m=0x8231d10, rank=2) at sr_module.c:785
#5 0x080e0e90 in init_mod_child (m=0x8231e20, rank=2) at sr_module.c:785
#6 0x080e0e90 in init_mod_child (m=0x8231ef8, rank=2) at sr_module.c:785
#7 0x080e0e90 in init_mod_child (m=0x82320e8, rank=2) at sr_module.c:785
#8 0x080e0e90 in init_mod_child (m=0x8232248, rank=2) at sr_module.c:785
#9 0x080e0e90 in init_mod_child (m=0x8232450, rank=2) at sr_module.c:785
#10 0x080e0e90 in init_mod_child (m=0x8232a70, rank=2) at sr_module.c:785
#11 0x080e0e90 in init_mod_child (m=0x8232c18, rank=2) at sr_module.c:785
#12 0x080a0b75 in fork_process (child_id=2,
desc=0xbfd5db7c "udp receiver child=1 sock=192.98.101.10:5060",
make_sock=1) at pt.c:329
#13 0x08088119 in main_loop () at main.c:1307
#14 0x0808ae4f in main (argc=-2082109099, argv=0x7d8928ec) at main.c:2108
19 Jul
19 Jul
6:07 p.m.
What'd you set db_mode to?
i have never used k dialog module because it is by far
the buggies
module that k has. now i ventured to try and, by no surprise, i crashed
sr before a single message went through. looks like it started to play
with db although i had not defined any.
-- juha
(gdb) where
#0 0x00000000 in ?? ()
#1 0xb728bba4 in dlg_connect_db (db_url=0xb72ab574) at
dlg_db_handler.c:119
#2 0xb72885e8 in child_init (rank=2) at dialog.c:576
#3 0x080e0f1b in init_mod_child (m=0x8231b20, rank=2) at sr_module.c:808
#4 0x080e0e90 in init_mod_child (m=0x8231d10, rank=2) at sr_module.c:785
#5 0x080e0e90 in init_mod_child (m=0x8231e20, rank=2) at sr_module.c:785
#6 0x080e0e90 in init_mod_child (m=0x8231ef8, rank=2) at sr_module.c:785
#7 0x080e0e90 in init_mod_child (m=0x82320e8, rank=2) at sr_module.c:785
#8 0x080e0e90 in init_mod_child (m=0x8232248, rank=2) at sr_module.c:785
#9 0x080e0e90 in init_mod_child (m=0x8232450, rank=2) at sr_module.c:785
#10 0x080e0e90 in init_mod_child (m=0x8232a70, rank=2) at sr_module.c:785
#11 0x080e0e90 in init_mod_child (m=0x8232c18, rank=2) at sr_module.c:785
#12 0x080a0b75 in fork_process (child_id=2,
desc=0xbfd5db7c "udp receiver child=1 sock=192.98.101.10:5060",
make_sock=1) at pt.c:329
#13 0x08088119 in main_loop () at main.c:1307
#14 0x0808ae4f in main (argc=-2082109099, argv=0x7d8928ec) at main.c:2108
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
6:14 p.m.
Very strange mystery. Needless to say I cannot reproduce this on K 1.5.x
proper.
Also, while I cannot comment on this deeply as I am not on the receiving
end of bug requests, it has not been my impression that the dialog module
is so buggy. Apart from the crashes I reported in the initial 1.5.0
release that were promptly resolved, I have not had any problems with it,
and have been using it with great success in fairly high-volume production
environments with K 1.5.1 and beyond.
Alex Balashov writes:
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
What'd you set db_mode to?
i didn't set it so anything:
5.10. db_mode (integer)
...
Default value is ??0??.
-- juha
6:23 p.m.
Alex Balashov writes:
Also, while I cannot comment on this deeply as I am
not on the receiving
end of bug requests, it has not been my impression that the dialog module
is so buggy. Apart from the crashes I reported in the initial 1.5.0
release that were promptly resolved, I have not had any problems with it,
and have been using it with great success in fairly high-volume production
environments with K 1.5.1 and beyond.
i'm basin my assumption about buggyness of dialog module just on the
large number bugs that has been reported and fixed during its lifetime.
according to some theory, the number of past bugs is an indication of
remaining ones.
-- juha
6:19 p.m.
i'm basin my assumption about buggyness of dialog
module just on the
large number bugs that has been reported and fixed during its lifetime.
according to some theory, the number of past bugs is an indication of
remaining ones.
-- juha
That seems believable, but I hope it is not true or I am really screwed!
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
6:29 p.m.
On 19.07.2009 17:23 Uhr, Juha Heinanen wrote:
Alex Balashov writes:
interesting theory. For 1.5.x the module was reshaped and there were not
so many bugs reported as for the past releases. However, probably more
care is good for it.
Hopefully, I fixed the issue you reported. Was a faulty condition,
probably introduced during migration and check of the PROC_TIMER child
that was causing out of sync for DB (reported some time ago).
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/index.php/sip-router-bootcamp/
Also, while I cannot comment on this deeply as I
am not on the receiving
end of bug requests, it has not been my impression that the dialog module
is so buggy. Apart from the crashes I reported in the initial 1.5.0
release that were promptly resolved, I have not had any problems with it,
and have been using it with great success in fairly high-volume production
environments with K 1.5.1 and beyond.
i'm basin my assumption about buggyness of dialog module just on the
large number bugs that has been reported and fixed during its lifetime.
according to some theory, the number of past bugs is an indication of
remaining ones.
6:24 p.m.
On 19.07.2009 17:14 Uhr, Alex Balashov wrote:
--
Daniel-Constantin Mierla
http://www.asipto.com/index.php/sip-router-bootcamp/
Very strange mystery. Needless to say I cannot
reproduce this on K 1.5.x
proper.
It is specific for devel version, probably introduced when DB
initialization was reshaped because of the new PROC_INIT rank. Should be
fixed now in git.
Also, while I cannot comment on this deeply as I am
not on the receiving
end of bug requests, it has not been my impression that the dialog module
is so buggy. Apart from the crashes I reported in the initial 1.5.0
release that were promptly resolved, I have not had any problems with it,
and have been using it with great success in fairly high-volume production
environments with K 1.5.1 and beyond.
I do use it in several deployments without any issue.
Cheers,
Daniel
Alex Balashov writes:
What'd you set db_mode to?
i didn't set it so anything:
5.10. db_mode (integer)
...
Default value is ??0??.
-- juha
5608
days inactive
5608
days old
7 comments
3 participants
participants (3)
-
Alex Balashov -
Daniel-Constantin Mierla -
jh＠tutpro.com