on in thread "main" java.lang.InternalError: Thread.start called but
> threads not available.
>
> I don't know what's this message.
> The J2sdk does work well under cygwin ? and Threads ?
> I think that's something in the cygwin .
>
> Can you help me ??
On Thu, 24 Jul 2003, P.B. Dushkin wrote:
> hi igor.
>
> right. thanks. i have tracked the culprit down
> and you are right.
>
> many thanks for responding.
>
> cheers,
> Peter
Peter,
I've set the Reply-To: on my previous message (and this one, BTW), please
make sure your mailer honors that. It'
ion in thread "main" java.lang.InternalError: Thread.start called
> but threads are not available.
>
> I have read through the list and it seems that this is a common problem
> with gcc but I am using the JDK under Cygwin (and ontop of XP).
>
> Any help at this point
. When I type "rmiregistry &" I get:
java.rmi.RemoteException: failed to export: class gnu.java.rmi.dgc.DGCImpl
Exception in thread "main" java.lang.InternalError: Thread.start called
but threads are not available.
I have read through the list and it seems that this is a
Hi all,
After i compile my java program using gcj in cygwin and execute the output file i get
"Thread.start called but threads not available"
When I check GCJ it seems it has been build with thread support (see below).
I compile using: gcj --main=Test -g0 -o test *java
A Test.jav
000:
gcj -o serveur --main=serveur serveur.java
The programme gave the following message about threads not available, but
gcc seems to be compiled with threads enable.
Why ?
Thanks for help,
[jgrelet]:/s/outils/sources/serveur> ./serveur 10183
Serveur version java 1.1 port UDP : 10183
Excep
> ./serveur 10183
Serveur version java 1.1 port UDP : 10183
Exception in thread "main" java.lang.InternalError: Thread.start called but
threads not available
[jgrelet]:/s/outils/sources/serveur> gcc -v
Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/specs
Configured with: /ne
7 matches
Mail list logo