[bug]: segmentation fault without bundled pjsip

Question

[bug]: segmentation fault without bundled pjsip

wbx-github opened this issue 3 months ago · comments

Waldemar Brodkorb commented 3 months ago

Severity

Trivial

Versions

20.7.0

Components/Modules

pjsip

Operating Environment

Hi,
I am using latest Buildroot on a Raspberry PI4 (64 Bit). I am maintaining the Asterisk package for Buildroot. Linux 6.1.61 with glibc 2.38 is used.

Frequency of Occurrence

Constant

Issue Description

With the bundled pjproject Asterisk works fine in my scenario. The Buildroot policy is not to download any source code while compiling a package. So I am trying to use the external pjproject 2.14.
But then Asterisk segfaults.

Relevant log output

gdb stacktrace:
(gdb) bt
#0  0x0000007fa12e4498 in strcmp () from /lib64/libc.so.6
#1  0x0000007f5bb2af84 in record_serializer (tdata=0x7f4c008f58) at res_pjsip/pjsip_distributor.c:85
#2  0x0000007f5bc856cc in endpt_on_tx_msg (endpt=0x55ab2d2b08, tdata=0x7f4c008f58) at ../src/pjsip/sip_endpoint.c:1116
#3  0x0000007f5bc8d028 in pjsip_transport_send (tr=0x55ab252748, tdata=tdata@entry=0x7f4c008f58, addr=addr@entry=0x7f4c009148, addr_len=addr_len@entry=16, token=token@entry=0x7f4c00a4e0, 
    cb=cb@entry=0x7f5bc87274 <stateless_send_transport_cb>) at ../src/pjsip/sip_transport.c:944
#4  0x0000007f5bc87480 in stateless_send_transport_cb (token=token@entry=0x7f4c00a4e0, tdata=tdata@entry=0x7f4c008f58, sent=<optimized out>) at ../src/pjsip/sip_util.c:1286
#5  0x0000007f5bc87afc in stateless_send_resolver_callback (status=<optimized out>, token=0x7f4c00a4e0, addr=<optimized out>) at ../src/pjsip/sip_util.c:1421
#6  0x0000007f5bb36c40 in sip_resolve_invoke_user_callback (data=0x7f4c00b698) at res_pjsip/pjsip_resolver.c:206
#7  0x00000055840e2180 in ast_taskprocessor_execute (tps=tps@entry=0x55ab3e59b8) at taskprocessor.c:1302
#8  0x00000055840e9080 in execute_tasks (data=0x55ab3e59b8) at threadpool.c:1350
#9  0x00000055840e2180 in ast_taskprocessor_execute (tps=0x55ab2d0e08) at taskprocessor.c:1302
#10 0x00000055840e7db4 in threadpool_execute (pool=0x55ab2d1958) at threadpool.c:367
#11 0x00000055840e7dd0 in worker_active (worker=worker@entry=0x7f50000be8) at threadpool.c:1137
#12 0x00000055840e83d0 in worker_start (arg=arg@entry=0x7f50000be8) at threadpool.c:1056
#13 0x00000055840efafc in dummy_start (data=<optimized out>) at utils.c:1607
#14 0x0000007fa12cf584 in ?? () from /lib64/libc.so.6
#15 0x0000007fa13351cc in ?? () from /lib64/libc.so.6

Asterisk Issue Guidelines

Yes, I have read the Asterisk Issue Guidelines

Joshua C. Colp · Answer 1 · Wed Mar 27 2024 16:43:23 GMT+0800 (China Standard Time)

Did this occur as a result of upgrading Asterisk? Was Asterisk actually built against the new headers? Looking at the backtrace and where it is, I would only expect such a crash if Asterisk was built against one set of headers but then used against another version or build of PJSIP.

Waldemar Brodkorb · Answer 2 · Thu Mar 28 2024 01:38:34 GMT+0800 (China Standard Time)

I double checked with a complete rebuild. (make clean && make)
The same issue happens. So this is not an update problem.

Joshua C. Colp · Answer 3 · Thu Mar 28 2024 01:42:52 GMT+0800 (China Standard Time)

What is the output of config.log for Asterisk?

Joshua C. Colp · Answer 4 · Thu Mar 28 2024 01:43:43 GMT+0800 (China Standard Time)

And what arguments were passed to pjproject for building it?

Joshua C. Colp · Answer 5 · Thu Mar 28 2024 01:44:55 GMT+0800 (China Standard Time)

Oh, and finally to confirm: the previous version of Asterisk was built against 2.13 and worked fine?

Joshua C. Colp · Answer 6 · Thu Mar 28 2024 01:54:39 GMT+0800 (China Standard Time)

I also built PJSIP 2.14 externally myself and built Asterisk 20.7.0 against it and confirmed bundled was not used. I ran outgoing call tests, which were successful and did not result in a crash.

Waldemar Brodkorb · Answer 7 · Thu Mar 28 2024 01:59:39 GMT+0800 (China Standard Time)

Oh, and finally to confirm: the previous version of Asterisk was built against 2.13 and worked fine?

The previous version 20.6.0 and the version included in Buildroot 20.5.2 having the same issues. May be pjsip is the problem?

Joshua C. Colp · Answer 8 · Thu Mar 28 2024 02:07:16 GMT+0800 (China Standard Time)

I can say that I am able to build both together not using bundled, and they work on my system. This would either mean it is your build process, the arguments passed to either PJSIP or Asterisk for building, or something in PJSIP that is only impacting things for you, or some other environmental thing. It doesn't appear to be an outright failure for all.

Waldemar Brodkorb · Answer 9 · Fri Mar 29 2024 13:52:31 GMT+0800 (China Standard Time)

Asterisk config.log
asterisk.config.log

Waldemar Brodkorb · Answer 10 · Fri Mar 29 2024 13:56:07 GMT+0800 (China Standard Time)

Pjsip config.log
pjsip.config.log

Joshua C. Colp · Answer 11 · Mon Apr 01 2024 03:13:34 GMT+0800 (China Standard Time)

I am still unable to reproduce this, so that means it is one of the following:

Something environment specific
Something build process specific
Something architecture specific
Something in PJSIP
A combination of the above
Something else

There's nothing else I can add or investigate, and this is in unsupported territory. I will leave it open to see if anyone else has experience or comments.

Waldemar Brodkorb · Answer 12 · Mon Apr 01 2024 11:04:55 GMT+0800 (China Standard Time)

The asterisk system is behind double NAT. But this works with the bundled pjsip as mentioned earlier.
I am attaching my extensions.conf and pjsip.conf for completeness. May be it is this special environment.
extensions.conf.txt
pjsip.conf.txt

George Joseph · Answer 13 · Mon Jun 17 2024 22:31:33 GMT+0800 (China Standard Time)

@wbx-github What config_site.h file are you using? You should be copying the one in <asterisk_src>/third-party/pjproject/patches to <pjproject_src>/pjlib/include/pj before configuring and building pjproject.