[sr-dev] Re: [kamailio/kamailio] Segfault in pua_dialoginfo.c when starting up with a dialog in the database (Issue #3743)
Closed #3743 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3743#event-12893838857 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
[sr-dev] Re: [kamailio/kamailio] Segfault in pua_dialoginfo.c when starting up with a dialog in the database (Issue #3743)
@xkaraman I confirm it no longer happens after updating to 5.8.1. Thanks! -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3743#issuecomment-2124140665 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
[sr-dev] Re: [kamailio/kamailio] Segfault in pua_dialoginfo.c when starting up with a dialog in the database (Issue #3743)
Hey again, i managed to reproduce it on 5.7.4 (also on 5.7.5) but it seems to be fixed in 5.8.1 and master already. Can you maybe verify that this is the case? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3743#issuecomment-2123058991 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
[sr-dev] Re: [kamailio/kamailio] Segfault in pua_dialoginfo.c when starting up with a dialog in the database (Issue #3743)
Hey @gianluca-nitti, Do you have any special config for the modules pua, dialog and pua_dialoginfo that you can provide? I am probably missing something when trying to replicate it with the provided dump and default configs. Thanks, -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3743#issuecomment-2122602174 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
[sr-dev] Re: [kamailio/kamailio] Segfault in pua_dialoginfo.c when starting up with a dialog in the database (Issue #3743)
Thanks for the response and sorry for the delay. I just found the dump I had took and tested that it still produces the same behavior (I'm currently on `version: kamailio 5.7.4 (x86_64/linux) ed9d7b`). Dump attached here [kamdb-dump.txt](https://github.com/kamailio/kamailio/files/15092499/kamdb-dump.txt). -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3743#issuecomment-2074610831 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
[sr-dev] Re: [kamailio/kamailio] Segfault in pua_dialoginfo.c when starting up with a dialog in the database (Issue #3743)
Thanks for providing the additional information. Does it crash only with the DB entry listed from above? If not, maybe you can provide the DB dump somewhere for download (sensitive data removed of course)? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3743#issuecomment-2049304633 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
[sr-dev] Re: [kamailio/kamailio] Segfault in pua_dialoginfo.c when starting up with a dialog in the database (Issue #3743)
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3743#issuecomment-2038658060 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
[sr-dev] Re: [kamailio/kamailio] Segfault in pua_dialoginfo.c when starting up with a dialog in the database (Issue #3743)
Thanks for the feedback and sorry for the delay.
I reproduced the crash today by importing the dump of the db I made when the
crash originally occurred.
I got 3 core dumps. Two have the backtrace as above, with `free_str_list_all`
at the top of the call stack, thus neither of those is (if I understand
correctly) the process from which the problem originated.
The third coredump has the following backtrace:
```
(gdb) bt full
#0 0x7ffa4c365840 in dialog_publish_multi
(state=state@entry=0x7ffa4c36c267 "terminated", ruris=0x2e656c706d617865,
entity=entity@entry=0x7ffd855c6440, peer=peer@entry=0x7ffd855c6450,
callid=callid@entry=0x7ffa5077cdf0,
initiator=initiator@entry=1, lifetime=10, localtag=0x0, remotetag=0x0,
localtarget=0x7ffa5077ce20, remotetarget=0x7ffd855c6430,
do_pubruri_localcheck=0, uuid=0x7ffa5077ce50)
at /usr/local/src/pkg/src/modules/pua_dialoginfo/dialog_publish.c:410
__llevel = 3
__func__ = "dialog_publish_multi"
#1 0x7ffa4c366f70 in __dialog_sendpublish (dlg=,
type=, _params=) at
/usr/local/src/pkg/src/modules/pua_dialoginfo/pua_dialoginfo.c:402
tag = {s = 0x0, len = 0}
uri = {
s = 0x7ffa5077ce7c
"sip:*9001*0039123456@example.voismart.commsowdcchfzrlapg@localhostmsfvzsip:*9001*0039123456@example.voismart.comsip:101_example_voismart_com@172.23.42.1:5065;alias=192.168.1.201~32878~1padi-1-65d7243e"...,
len = 41}
identity_local = {
s = 0x7ffa5077ce60
"sip:101@example.voismart.comsip:*9001*0039123456@example.voismart.commsowdcchfzrlapg@localhostmsfvzsip:*9001*0039123456@example.voismart.comsip:101_example_voismart_com@172.23.42.1:5065;alias=192.168."...,
len = 28}
target = {s = 0x0, len = 0}
dlginfo = 0x7ffa5077cdc8
request = 0x0
__func__ = "__dialog_sendpublish"
#2 0x7ffa4f0b5867 in run_dlg_callbacks (type=64, dlg=0x7ffa500318a0,
req=, rpl=, dir=,
dlg_data=) at /usr/local/src/pkg/src/modules/dialog/dlg_cb.c:269
cb = 0x7ffa5077d050
__func__ = "run_dlg_callbacks"
#3 0x7ffa4f115df7 in dlg_bye_all (dlg=0x7ffa500318a0, hdrs=0x0) at
/usr/local/src/pkg/src/modules/dialog/dlg_req_within.c:858
all_hdrs = {s = 0x0, len = 0}
ret =
__func__ = "dlg_bye_all"
#4 0x7ffa4f0e6669 in dlg_ontimeout (tl=0x7ffa50031900) at
/usr/local/src/pkg/src/modules/dialog/dlg_handlers.c:1670
dlg = 0x7ffa500318a0
new_state = 22098
old_state = 72604856
unref = 22098
fmsg =
timeout_cb = 0x0
keng =
evname = {s = 0x4b , len =
72378941}
__func__ = "dlg_ontimeout"
#5 0x7ffa4f109460 in dlg_timer_routine (ticks=,
attr=) at /usr/local/src/pkg/src/modules/dialog/dlg_timer.c:281
tl = 0x0
ctl = 0x7ffa50031900
__func__ = "dlg_timer_routine"
#6 0x56520433e01b in compat_old_handler (ti=, tl=, data=) at core/timer.c:980
t =
#7 0x565204353c29 in slow_timer_main () at core/timer.c:1103
n =
ret =
tl = 0x7ffa4ff1f428
i =
__func__ = "slow_timer_main"
#8 0x5652040c2fec in main_loop () at /usr/local/src/pkg/src/main.c:1490
i =
pid =
--Type for more, q to quit, c to continue without paging--
si =
si_desc = "udp receiver child=31
sock=172.23.42.2:\000RV\000\000\000
\034X\372\177\000\000\003\000\000\000\377\377\377\377\004`P\004RV\000\000\004\000\000\000\372\177\000\000\003\000\000\000\000\000\000\000\t\000\000\000\000\000\000\000Thu
Feb \000qv1\335c\376\356:54 2024\005\000\000\000\000\000\000"
nrprocs =
woneinit = 1
error =
__func__ = "main_loop"
#9 0x5652040b6ffc in main (argc=, argv=) at
/usr/local/src/pkg/src/main.c:3212
cfg_stream =
c =
r =
tmp = 0x7ffd855c8db4 ""
tmp_len = 0
port = 32765
proto = -2057539472
ahost = 0x0
aport = 0
options = 0x565204509300
":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:"
ret = -1
seed = 1294483928
rfd =
debug_save =
debug_flag =
dont_fork_cnt =
n_lst =
p =
st = {st_dev = 198, st_ino = 827616256, st_nlink = 1, st_mode = 16872,
st_uid = 101, st_gid = 101, __pad0 = 0, st_rdev = 0, st_size = 6, st_blksize =
4096, st_blocks = 0, st_atim = {tv_sec = 1708594589,
tv_nsec = 533404421}, st_mtim = {tv_sec = 1708598142, tv_nsec =
117863927}, st_ctim = {tv_sec = 1708598142, tv_nsec = 117863927},
__glibc_reserved = {0, 0, 0}}
tbuf = '\000' , '/' , "\230\r",
'\000' , "`", '\000' , "\001", '\000'
...
option_index = 12
__func__ = "main"
long_options = {{name = 0x565204508fe2 "help", has_arg = 0, flag = 0x0,
val = 104}, {name = 0x565204510dc8 "version", has_arg = 0, flag = 0x0, val =
118}, {name = 0x565204520731 "alias", has_arg = 1, flag = 0x0,
val = 1024}, {name =
[sr-dev] Re: [kamailio/kamailio] Segfault in pua_dialoginfo.c when starting up with a dialog in the database (Issue #3743)
The corefile from where you got the attached backtrace is generated at shut down, it is not the one that caused the crash, but a side effect as the structures might be compromised at that phase. Practically the above backtrace does not reflect the reason of the real crash. You have to enable core file per pid and get the backtraces from all core files. >From the log messages, there is a hint that the R-URI is invalid, maybe you do >some operations in config that break it. Anyhow, it would be good to get it >caught, crashing should not happen even with a config-made invalid R-URI. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3743#issuecomment-1935454766 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
