Re: [sr-dev] [kamailio/kamailio] Segmentation fault using http_async_client on kamailio 5.0.0 (#1056)
@davyvdm - have you been able to test with patches from PR #1063? Is all going fine with them? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1056#issuecomment-292954660___ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Segmentation fault using http_async_client on kamailio 5.0.0 (#1056)
The issue is in the tm module. While processing the resumed reply, since we are in a case of final reply for the transaction, we delete it after sending it out. This is causing the carsh when, at the end of t_continue we try to access the branch's reply. I've open a PR https://github.com/kamailio/kamailio/pull/1063 with a fix. Also, why do you need to suspend the reply in this case? Wouldn't be fine to not suspend the transaction? See $http_req(suspend) http://www.kamailio.org/docs/modules/devel/modules/http_async_client.html#idp21739572. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1056#issuecomment-292656252___ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Segmentation fault using http_async_client on kamailio 5.0.0 (#1056)
I'm sorry, I've been quite busy in the last days. I will try to reproduce/investigate this in the next days. The function should indeed work in the scenario. @davyvdm: to be clear, are you calling http_async_query in a reply route or in a failure route? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1056#issuecomment-292451830___ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Segmentation fault using http_async_client on kamailio 5.0.0 (#1056)
@davyvdm ok, wanted to clarify -- maybe Federico ( @grumvalski ) can assert if the function is expected to run for sip replies or not, and investigate if does the expected behaviour in this case. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1056#issuecomment-291856051___ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Segmentation fault using http_async_client on kamailio 5.0.0 (#1056)
@miconda that is correct, when I put the snippet elsewhere (not in reply_route), there is no issue... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1056#issuecomment-291851809___ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Segmentation fault using http_async_client on kamailio 5.0.0 (#1056)
@davyvdm - your config snippet is from a reply_route (executed when handling a SIP response)? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1056#issuecomment-291848425___ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Segmentation fault using http_async_client on kamailio 5.0.0 (#1056)
@linuxmaniac thank you for the remark ;) updated it -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1056#issuecomment-291827091___ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Segmentation fault using http_async_client on kamailio 5.0.0 (#1056)
@davyvdm please use the proper format (insert code) when pasting gdb output or github gets confused -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1056#issuecomment-291820444___ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Segmentation fault using http_async_client on kamailio 5.0.0 (#1056)
Using kamailio-dbg:
Reading symbols from /usr/sbin/kamailio...Reading symbols from
/usr/lib/debug/.build-id/fe/4d6c322f76df685bbec9adafde99fc43c0bc6a.debug...done.
done.
[New LWP 11891]
[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'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f226e50760a in t_continue (hash_index=1984, label=122428216,
route=0x7f2270bb15f0) at t_suspend.c:411
411 t_suspend.c: No such file or directory.
(gdb) bt full
#0 0x7f226e50760a in t_continue (hash_index=1984, label=122428216,
route=0x7f2270bb15f0) at t_suspend.c:411
t = 0x7f2262786938
faked_req = 0x7f226e4763a1
faked_req_len = 0
cancel_data = {cancel_bitmap = 0, reason = {cause = 0, u = {text = {s =
0x0, len = 2}, e2e_cancel = 0x0, packed_hdrs = {s = 0x0, len = 2
branch = 0
uac = 0x0
ret = 32765
cb_type = 3
msg_status = 32765
last_uac_status = 1646426056
reply_status = 4
do_put_on_wait = 1
hdr = 0x0011
prev = 0x0
tmp = 0x0
route_type_bk = 32546
__FUNCTION__ = "t_continue"
#1 0x7f226c317848 in async_http_cb (reply=0x7f22627d9d28,
param=0x7f22626d16f8) at async_http.c:217
aq = 0x7f22626d16f8
act = 0x7f2270bb15f0
tindex = 1984
tlabel = 122428216
t = 0x7f2262786938
p = 0x0
newbuf = {s = 0x0, len = 0}
fmsg = 0x26c3860
__FUNCTION__ = "async_http_cb"
#2 0x7f226c311a72 in check_multi_info (g=0x7f22626ac5a8) at
http_multi.c:573
eff_url = 0x26cd640 "https://109.68.161.209:9443/customers/cdr/";
msg = 0x26c3880
msgs_left = 0
easy = 0x26c3860
res = CURLE_OK
cell = 0x7f226279b068
__FUNCTION__ = "check_multi_info"
#3 0x7f226c3096a4 in event_cb (fd=11, kind=2, userp=0x26c3860) at
http_multi.c:145
g = 0x7f22626ac5a8
rc = CURLM_OK
easy = 0x26c3860
cell = 0x7f226279b068
__FUNCTION__ = "event_cb"
action = 1
#4 0x7f226be483dc in event_base_loop () from
/usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
No symbol table info available.
#5 0x7f226c314c3d in async_http_run_worker (worker=0x7f2262418430) at
async_http.c:86
No locals.
#6 0x7f226c2fe86e in child_init (rank=0) at http_async_client_mod.c:367
---Type to continue, or q to quit---
pid = 0
i = 0
__FUNCTION__ = "child_init"
#7 0x0053d8c2 in init_mod_child (m=0x7f2270a5d5c8, rank=0) at
core/sr_module.c:921
__FUNCTION__ = "init_mod_child"
#8 0x0053d5e0 in init_mod_child (m=0x7f2270a5e1e0, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#9 0x0053d5e0 in init_mod_child (m=0x7f2270a5e850, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#10 0x0053d5e0 in init_mod_child (m=0x7f2270a5edb0, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#11 0x0053d5e0 in init_mod_child (m=0x7f2270a5f420, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#12 0x0053d5e0 in init_mod_child (m=0x7f2270a5f8d0, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#13 0x0053d5e0 in init_mod_child (m=0x7f2270a5ffe8, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#14 0x0053d5e0 in init_mod_child (m=0x7f2270a60440, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#15 0x0053d5e0 in init_mod_child (m=0x7f2270a607e8, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#16 0x0053d5e0 in init_mod_child (m=0x7f2270a60b88, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#17 0x0053d5e0 in init_mod_child (m=0x7f2270a60fc8, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#18 0x0053d5e0 in init_mod_child (m=0x7f2270a61370, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#19 0x0053d5e0 in init_mod_child (m=0x7f2270a61780, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#20 0x0053d5e0 in init_mod_child (m=0x7f2270a61bc8, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#21 0x0053d5e0 in init_mod_child (m=0x7f2270a62380, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#22 0x0053d5e0 in init_mod_child (m=0x7f2270a62c00, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#23 0x0053d5e0 in init_mod_child (m=0x7f2270a65608, rank=0) at
core/sr_module.c:918
__FUNCTION__ = "init_mod_child"
#24 0x0053d5e0 in init_mod_child (m=0x7f2270a66290, rank=0) at
core/sr_module.c:918
Re: [sr-dev] [kamailio/kamailio] Segmentation fault using http_async_client on kamailio 5.0.0 (#1056)
Also, install kamailio-dbg package (which has the debug symbols) and grab again the backtrace, it will be more useful. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1056#issuecomment-291780434___ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Re: [sr-dev] [kamailio/kamailio] Segmentation fault using http_async_client on kamailio 5.0.0 (#1056)
Could you please describe the procedure to reproduce the segfault and, in case, the relevant part of your config? Thanks. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1056#issuecomment-291761660___ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
