This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: JNI issues

To: Bryce McKinlay <bryce at albatross dot co dot nz>
Subject: Re: JNI issues
From: Cedric Berger <cedric at wireless-networks dot com>
Date: Wed, 31 Jan 2001 08:29:02 -0800
CC: martin dot kahlert at infineon dot com, Tom Tromey <tromey at redhat dot com>, java-discuss at sourceware dot cygnus dot com
References: <20010130154422.A14301@keksy.muc.infineon.com> <87d7d50xqg.fsf@creche.redhat.com> <20010131092455.B19572@keksy.muc.infineon.com> <3A77ED23.68F8BA80@albatross.co.nz>

>
> The basic problem here is that the current thread was not started with the
> normal thread startup sequence (ie "new Thread(); thread.start();") so does not
> have any Java thread object/data associated with it. We need to implement a
> mechanism such that a java.lang.Thread (and other data used by the runtime) can
> get "attached" to an already running thread.
> 
That would be AttachCurrentThread() ?

References:
- JNI issues
  - From: Martin Kahlert
- Re: JNI issues
  - From: Tom Tromey
- Re: JNI issues
  - From: Martin Kahlert
- Re: JNI issues
  - From: Bryce McKinlay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]