CNI threads and garbage collection on FC5

["Martin, Craig W" <Craig dot Martin2 at xerox dot com>]

All,

First let me thank all of you for the wonderful work you do on GCC and all its derivatives.  Awesome work!

Recently I ran into a curious problem though, an application that uses CNI threads seems to fail with "collecting from unknown thread" and "null pointer exceptions" in Core 5.  This application runs beautifully under Core 3 and 4, so something has changed under the Core 5 GCJ stuff  that I can't pinpoint.  I was unable to make my application run under core 5 without killing the GC and eventually went back to core 4.  My problems are very similar to those discussed in:

http://gcc.gnu.org/ml/java/2005-08/msg00147.html

except that mine occur on Core 5 with GCJ 4.1.x.  I should note also that all my threads are started from compiled Java classes as discussed in the aforementioned URL.  I also noted that my CNI based shared libraries (originally two of them) had to be merged into one to get things to link (seemed strange to me).  Don't know if this is related to the problem.

Is there any possibility that something foundational has changed in GCJ that I am unaware of?  I am concerned because as I port to more recent versions of Linux I fear my application will continue to fail until I understand what changed in GCJ 4.1 that caused these issues.  Any pointers as to what I may be missing would be most welcome.

Best regards,

Craig Martin