This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/13212] JNI/CNI AttachCurrentThread does not register thread with garbage collector
- From: "greenrd at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 Oct 2005 10:44:47 -0000
- Subject: [Bug libgcj/13212] JNI/CNI AttachCurrentThread does not register thread with garbage collector
- References: <bug-13212-7355@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #18 from greenrd at gcc dot gnu dot org 2005-10-23 10:44 -------
Arno - you're missing the point. One of the test cases for this is rssowl (or
more specifically, the SWT Browser widget, which embeds Mozilla on Linux). The
Mozilla embedding subsystems (as opposed to the Mozilla Java plugin system,
which is called OJI) don't know anything about CNI/JNI, so they can't be
expected to create threads using the wrapped call to pthread_create.
In general, AttachCurrentThread must be able to deal with arbitrary threads
created by third-party native code which doesn't know about CNI or JNI. The
current implementation cannot cope with arbitrary threads. See the discussion
on the fedora Java mailing list.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13212