public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "stewart at neuron dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/13212] JNI/CNI AttachCurrentThread does not register thread with garbage collector
Date: Fri, 07 Oct 2005 13:49:00 -0000 [thread overview]
Message-ID: <20051007134917.2805.qmail@sourceware.org> (raw)
In-Reply-To: <bug-13212-7355@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from stewart at neuron dot com 2005-10-07 13:49 -------
(In reply to comment #9)
> Yes, I'm sure. I know what's going on here.
>
This is the only bug I was able to find regarding AttachCurrentThread. I'm
working on getting FUSE-J (Java bindings for FUSE userspace filesystem) working
with GCJ and have run across an apparent bug with
AttachCurrentThread/AttachCurrentThreadAsDaemon whereby the returned JNIEnv has
a corrupted pointer to CallObjectMethod. I emailed the following to <tromey at
redhat dot com>:
You should be able to setup/reproduce this quickly. First is to
get/build/install the fuse library:
http://fuse.sourceforge.net/
http://easynews.dl.sourceforge.net/sourceforge/fuse/fuse-2.4.0.tar.gz
./configure --prefix=/usr/local &&
make &&
make install &&
depmod -a &&
modprobe fuse
Second, get fuse-j, the java language bindings
http://www.select-tech.si/fuse/
http://www.select-tech.si/fuse/fuse-j-2.2.3.tar.gz
get and apply my patch for gcj:
http://mrallen.com/misc/fuse-j-2.2.3-gcj.diff
inside fuse-j-2.2.3:
patch -p1 < path_to_patch
then you will need a zip file to test and a mount point. next:
make
sh zipfs_gcj.sh <zip_file> <mount_point>
once it's running, doing a 'df' in another term will crash cause the segfault.
you will have to have /usr/local/bin in your PATH and execute 'fusermount -u
<mount_point>' to undo the mount. (In reply to comment #9)
> Yes, I'm sure. I know what's going on here.
>
--
stewart at neuron dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stewart at neuron dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13212
next parent reply other threads:[~2005-10-07 13:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13212-7355@http.gcc.gnu.org/bugzilla/>
2005-10-07 13:49 ` stewart at neuron dot com [this message]
2005-10-12 18:11 ` tromey at gcc dot gnu dot org
2005-10-12 20:29 ` stewart at neuron dot com
2005-10-22 20:58 ` arno at heho dot snv dot jussieu dot fr
2005-10-23 0:21 ` arno at heho dot snv dot jussieu dot fr
2005-10-23 0:22 ` arno at heho dot snv dot jussieu dot fr
2005-10-23 0:24 ` arno at heho dot snv dot jussieu dot fr
2005-10-23 0:28 ` arno at heho dot snv dot jussieu dot fr
2005-10-23 10:44 ` greenrd at gcc dot gnu dot org
2005-10-23 23:37 ` arno at heho dot snv dot jussieu dot fr
2006-01-09 17:25 ` aph at gcc dot gnu dot org
2006-01-09 17:32 ` greenrd at gcc dot gnu dot org
2006-01-09 17:41 ` jakub at gcc dot gnu dot org
2006-01-09 17:43 ` jakub at gcc dot gnu dot org
2006-01-09 18:21 ` cagney at redhat dot com
2006-01-13 22:44 ` tromey at gcc dot gnu dot org
2006-03-24 14:08 ` rguenth at gcc dot gnu dot org
2006-03-24 15:35 ` rguenth at gcc dot gnu dot org
2006-03-24 17:41 ` aph at gcc dot gnu dot org
2006-03-25 1:07 ` matz at suse dot de
2006-03-30 7:00 ` mckinlay at redhat dot com
2006-03-30 15:48 ` rguenth at gcc dot gnu dot org
2006-03-30 15:51 ` mckinlay at redhat dot com
2006-05-22 16:16 ` rguenth at gcc dot gnu dot org
2006-06-10 18:00 ` arno at heho dot snv dot jussieu dot fr
2006-07-14 14:02 ` davidf at sjsoft dot com
2006-08-21 22:07 ` tromey at gcc dot gnu dot org
2006-08-21 22:09 ` tromey at gcc dot gnu dot org
2006-09-01 16:16 ` tromey at gcc dot gnu dot org
[not found] <20031127132523.13212.alessio@itapac.net>
2005-09-11 2:59 ` david at jpackage dot org
2005-09-11 3:02 ` billy dot biggs at gmail dot com
2005-09-15 0:27 ` greenrd at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051007134917.2805.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).