The first core is relevant, the other one is because kamailio tries to shut
down due to other process crash, but ends in a deadlock, likely because the
process that crashed didn't release a lock.
In the fist core, the problem seems to be in the odbc driver - the backtrace
leaves the code of kamailio with the next frames:
```
#29 0x00007fbc4ec17c66 in SQLDriverConnectW () from
/opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.0.so.0.0
No symbol table info available.
#30 0x00007fbc565deabd in SQLDriverConnect (hdbc=0x1121920,
hwnd=0x7ffd06240460, conn_str_in=0x1142cb0 "D", len_conn_str_in=25892,
conn_str_out=0x7ffd0624bf60 "\001\200\255\373\274\177", conn_str_out_max=0,
ptr_conn_str_out=0x7ffd0624bf5e, driver_completion=1) at SQLDriverConnect.c:1490
uc_conn_str_in = 0x1142cb0
```
Not sure I can really help much more here.
Can you test with other versions of odbc and ms odbc drivers?
Does libmsodbcsql has a package for debug symbols? Or, if libmsodbcsql is open
source, maybe you can install it from sources with debug symbols on. Then the
backtrace will show where in the source code of libmsodbcsql the crash happens
and from there further investigation can be done in order to spot the problem.
---
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/501#issuecomment-198356246_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
