Control: forwarded -1 http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2016-November/019636.html
On Thu, Nov 03, 2016 at 03:12:37PM -0400, Gedalya wrote: Hi, > > Confirmed. If you start Asterisk in the foreground you actually get an > > assertion > > > > asterisk: ../src/pj/os_core_unix.c:1254: pj_mutex_lock: Assertion > > `mutex' failed. > > Aborted > > > > Haven't done any further debugging until now, since we can't build > > asterisk. > > Hi, > > I decided to try this: I made a sid chroot, manually downgraded to libssl-dev > 1.0.2j-1 from stretch, and built asterisk from the current packaging git head > (ec0143a). > I actually enabled OpenSSL-1.1.0-support.patch while I was at it. > > Ultimately, running this with pjproject 2.5.5~dfsg-2 failed at the same > stage, but with a different assert: > > asterisk: ../src/pjsip/sip_auth_client.c:507: pjsip_auth_clt_deinit: > Assertion `sess && sess->endpt' failed. > Aborted Thanks. I have also tested that a fresh rebuild of 2.5.1 does not exhibit the problem, so it is not caused by updated build-deps. Upstream recommends to disable assertions in production builds, see https://trac.pjsip.org/repos/wiki/FAQ#assert When I do this I get a full-blown segfault (and we lose a symbol, so although we only have one rdep it would technically involve a library transition). I've reported the segfault to the upstream mailinglist I will try the latest SVN snapshot later. Bernhard
signature.asc
Description: Digital signature
