Node:Known Bugs and Limitations in Jasper, Next:Java Examples Directory, Previous:Multi threading, Up:Jasper Notes
native. This is due to a
security-restriction enforced on applets by Java; they are not allowed to call
native code.
green threads). This is the default under Windows. Under UNIX,
most JDKs use native threads per default in version 1.2.
On some platforms, you need to explicitly specify the -native
option when calling java. The following error is an example of
what may happen if you do not specify -native:
% java -classpath .:[...]/lib/sicstus-3.9.1/bin/jasper.jar \
-Djava.library.path=[...]/lib \
-Dsicstus.path=[...]./lib/sicstus-3.9.1 Simple
*** panic: libthread loaded into green threads
Abort (core dumped)
Instead, do
% java -native [...]this should not be neede with JDK 1.3 or newer.
See your JDK documentation for more info on command-line parameters to the JVM.
SPTerm will leak memory on the Prolog side. This is
not really a bug but may come as a surprise to the unwary. See SPTerm and Memory.
% splfr simple.pl
SICStus 3.8.7 (sparc-solaris-5.7): Mon Feb 21 10:43:17 MET 2000
Licensed to SICS
{spk.ai82.c generated, 20 msec}
yes
In file included from /usr/local/jdk1.2/include/jni.h:35,
from spk.ai82.c:94:
/usr/local/jdk1.2/include/solaris/jni_md.h:20: warning: \
ignoring pragma: "@(#)jni_md.h 1.11 99/02/01 SMI
The warning can be safely ignored. You can suppress the warnings when
using gcc by
passing the options --cflag=-Wno-unknown-pragmas to splfr.