Re: [Linphone-developers] Runtime Errors

[Greg Troxel]

"Raghav Gururajan" <address@hidden> writes:

> I am in the middle of packaging LinphoneQt (4.1.1) into Guix System 
> (https://guix.gnu.org).
>
> While running the application, I get the following errors and application 
> quits itself:
>
> QMutex: destroying locked mutex
> Core:belle-sip: There were still [1] object pools for thread 
> [140700444260096] while the thread exited.

Probably you know this, but the pthreads/mutex specs are pretty
unforgiving.  Many things, including destroying a locked mutex, are
undefined behavior.  Some systems seem to be set up to basically ignore
those things, and somesystems seem to be set up to basically assert on
undefined behavior.  NetBSD used to assert, and then ran into too many
problems with incorrect code that worked on Linux (and therefore did not
get fixed), and I think we changed those to ignore.

1) you may have a runtime switch (env var) to control asserting vs
reporting vs ignoring on undefined behavior.  An example, perhaps useful
only as a hint of what to look for:
  https://netbsd.gw.com/cgi-bin/man-cgi?pthread+3+NetBSD-current

2) it may be possible to add a breakpoint for that error case and figure
out why the mutex wasn't unlocked before being destroyed.


(I don't know if this is fixed post 4.1.1.)