This is the mail archive of the
java-patches@sourceware.cygnus.com
mailing list for the Java project.
Re: PATCH: Threads and SIGINT
- To: Bryce McKinlay <bryce at albatross dot co dot nz>
- Subject: Re: PATCH: Threads and SIGINT
- From: Joerg Brunsmann <joerg dot brunsmann at FernUni-Hagen dot de>
- Date: Thu, 23 Dec 1999 19:11:39 +0100
- CC: java-patches at sourceware dot cygnus dot com
- Organization: Fernuniversitaet Hagen - Software Engineering (Praktische Informatik III)
- References: <3861C24E.D1C0428C@albatross.co.nz>
Bryce McKinlay wrote:
> Regarding the Solaris thread problems reported by Joerg Brunsmann: I have
> reproduced this on my Solaris x86 installation, and I'm convinced that these
> problems are in fact due to a bug in Solaris rather than anything wrong with our
> code. Solaris 7 (and I presume some 2.6 installations as well, since Joerg
> reports that he is using 2.6) have a broken recursive mutex implementation,
> resulting in calls to pthread_cond_wait never returning because it cannot
> reacquire the mutex.
If I was reporting that I'm using 2.6 I was definitly wrong. I'm using 2.7 where
I see the bug. Due to coincidence I noticed the solaris bug report as well. I
searched the latest sunsolve CDs but didn't find a patch. So I tried to install
gcj/libgcj on a Solaris 2.6 machine in order to verify if the problem persists
with that OS version. But unfortunately gcj compiled programs dump core. I kept
calm because lack of time and christmas/millenium/solaris 8 right around the
corner.
> In order to fix this I think we need to force the use of default, non-recursive
> mutexes on Solaris. I think this could be done with something like "#if defined
> (SOLARIS && HAVE_PTHREAD_MUTEX_SETTYPE) #undef HAVE_PTHREAD_MUTEX_SETTYPE" at
> the top of posix-threads.h, but perhaps there is a better way.
This might be a good temporarely work around. Then we wait for Solaris 8
or a patch for Solaris 7 or Solaris source code in order to fix it...
Happy christmas,
Jörg