Subject: pkg/21481: wxGTK (or other related libs) triggers libpthread assertions
To: None <email@example.com>
From: None <firstname.lastname@example.org>
Date: 05/06/2003 17:39:27
>Synopsis: wxGTK (or other related libs) triggers libpthread assertions
>Arrival-Date: Tue May 06 15:40:00 UTC 2003
>Release: NetBSD 1.6R
Julio M. Merino Vidal <email@example.com>
The NetBSD Project - http://www.NetBSD.org/
System: NetBSD darkstar.local 1.6R NetBSD 1.6R (DARKSTAR) #6: Sun May 4 13:56:22 CEST 2003 firstname.lastname@example.org:/p/home/jmmv/obj i386
After all the new assertion control has been added to current's
libpthread, some programs have stopped working. They trigger an
assertion during their startup and then the program aborts.
Here is an example:
assertion "weown" failed: file "/pool/usr/src/lib/libpthread/pthread_mutex.c", line 332, function "pthread_mutex_unlock"
 Abort trap (core dumped) PTHREAD_ERRORMOD...
As Nathan explained, this problem is related with the program itself
or any of its libraries, but not with our own libpthread code.
The code is trying to free a mutex that has not been initialized.
I've found that lmule, audacity and poedit fail with the same
problem. As all of them use the wxGTK library, it seems the bug
is located in it; it might also be in any other related library.
Install any of the programs mentioned above (lmule, audacity or
poedit) and run them. They will fail just after the main window
opens (at least for lmule).