OK, getting closer :). Let's see who is the proc ID 46.

In GDB, just do

> p pt[46]

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
  https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 10/7/21 3:37 PM, Andrew Yager wrote:
Hi Bogdan-Andrei,

OK; my non expert opinion is that these two lines in ipc.c may be a pointer to a "symptom" of the problem…

// FIXME - we should check if the destination process really listens
// for read, otherwise we may end up filling in the pipe and block

but, I really want to know why it's blocking on the IPC comms before that.

Here's the BT.

(gdb) bt full
#0  0x00007f1e4ce9b297 in __libc_write (fd=fd@entry=195, buf=buf@entry=0x7fffc86261b0, nbytes=nbytes@entry=24) at ../sysdeps/unix/sysv/linux/write.c:26
        resultvar = 18446744073709551104
        __arg3 = <optimized out>
        _a2 = <optimized out>
        sc_ret = <optimized out>
        __arg1 = <optimized out>
        _a3 = <optimized out>
        sc_cancel_oldtype = <optimized out>
        resultvar = <optimized out>
        resultvar = <optimized out>
        __arg2 = <optimized out>
        _a1 = <optimized out>
#1  0x000055ddea5cad33 in __ipc_send_job (payload2=0x0, payload1=0x55ddea590760 <rpc_get_pkg_stats>, type=0, fd=195) at ipc.c:171         job = {snd_proc = 1, handler_type = 0, payload1 = 0x55ddea590760 <rpc_get_pkg_stats>, payload2 = 0x0}
        n = <optimized out>
        job = <optimized out>
        n = <optimized out>
        __FUNCTION__ = "__ipc_send_job"
#2  ipc_send_rpc (dst_proc=dst_proc@entry=46, rpc=rpc@entry=0x55ddea590760 <rpc_get_pkg_stats>, param=param@entry=0x0) at ipc.c:194

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to