libgcj/13

[Bryce McKinlay]

The following reply was made to PR libgcj/13; it has been noted by GNATS.

From: Bryce McKinlay <bryce@albatross.co.nz>
To: John Stracke <francis@thibault.org>
Cc: tromey@cygnus.com, java-gnats@sourceware.cygnus.com
Subject: Re: libgcj/13
Date: Fri, 03 Mar 2000 09:42:48 +1300

 John Stracke wrote:
 
 > Bryce McKinlay wrote:
 >
 > > What version of gcj & libgcj are you using? And what platform?
 >
 > gcc 2.95.2, libgcj 2.95.1 (the most recent I could find), on RedHat 6.1, with no
 > particular flags to configure except for --prefix (didn't want to make a mistake
 > and blow away the bundled gcc).  Oh, and --enable-shared (for gcc, not for
 > libgcj).
 >
 > I also tried it with --enable-threads=posix.
 
 Even though 2.95.1 is our most recent release, it is very outdated. There are many
 fixes relating to threads and gc in libgcj cvs and snapshot releases. So far we
 havn't been able to do a new release because it depends on changes in the compiler.
 
 Try a snapshot from ftp://sourceware.cygnus.com/pub/java/snapshot
 
 You'll also need a snapshot gcc to compile it. If you don't want to use an unstable
 compiler, you can try my java patch for gcc-2.95.2 which is at
 http://waitaki.otago.ac.nz/~bryce/gcj
 
 
 > > PR libgcj/13 was fixed a long time ago, and I doubt its the cause of your
 > > problem.
 >
 > You're right; it seems to be a more general problem.  Here's a test case where the
 > parent thread hangs until the child terminates, even though the child isn't doing
 > any I/O.
 
 I don't see what the problem is here. Are you expecting the application to shut down
 when main() returns? The app should not exit until all non-daemon threads have died.
 
 regards
 
   [ bryce ]