Subject: Re: pkg/30210: Thread problem in openoffice-1.1.4nb2
To: None <mrauch@netbsd.org, gnats-admin@netbsd.org, pkgsrc-bugs@netbsd.org>
From: Michael Rauch <mrauch@NetBSD.org>
List: pkgsrc-bugs
Date: 05/13/2005 17:08:02
The following reply was made to PR pkg/30210; it has been noted by GNATS.

From: Michael Rauch <mrauch@NetBSD.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: pkg/30210: Thread problem in openoffice-1.1.4nb2
Date: Fri, 13 May 2005 19:07:20 +0200

 Hi, 
 
 On Thu, May 12, 2005 at 04:57:00AM +0000, smb@cs.columbia.edu wrote:
 > >Synopsis:       Thread problem in openoffice-1.1.4nb2
 > [...]
 > 	Thread problem in openoffice-1.1.4nb2:
 > 
 > 	soffice.bin: Error detected by libpthread: Destroying locked mutex.
 > 	Detected by file "/usr/src/lib/libpthread/pthread_mutex.c", line 135, function "pthread_mutex_destroy".
 > 	See pthread(3) for information.
 > 
 > 	I had a number of Powerpoint files open at the time.  The one
 > 	I was viewing had a very complex set of graphics which took a
 > 	long time to render; I had hit pagedown while waiting for it
 > 	to render.
 
 and then it did what? Crash? Continue to work? 
 NetBSD's pthread implementation has many internal consistency checks,
 that other thread implementations (like Linux) don't have and don't
 complain about related errors.
 That thread-related problems do exist in OpenOffice is known, so it
 depends on the exact circumstances what can be done, and is worth the
 effort.
 Btw, do you set PTHREAD_DIAGASSERT in your shell? There's already the
 standard setting in the startup script to ignore all pthread-related
 errors it can, but this only takes effect if this variable is unset. 
 
 
 Michael