my last email is include below. I've now looked into whether the .so files use
ioctl:
nm libtclblend.so | grep ioctl
gives
U ioctl
and
ldd libtclblend.so
gives
libthread.so.1 => /usr/lib/libthread.so.1
libjava.so => /usr/java1.2/jre/lib/sparc/libjava.so
libdl.so.1 => /usr/lib/libdl.so.1
libsocket.so.1 => /usr/lib/libsocket.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libm.so.1 => /usr/lib/libm.so.1
libc.so.1 => /usr/lib/libc.so.1
libjvm.so => /usr/java1.2/jre/lib/sparc/libjvm.so
libmp.so.2 => /usr/lib/libmp.so.2
/usr/platform/SUNW,Ultra-5_10/lib/libc_psr.so.1
when a nm is done on these files the following seem to use ioctl:
libc.so
libnsl.so
libsocket.so.1
libjvm.so
In my LD_LIBRARY_PATH I have /usr/lib where these .so files are located, but
still I get the error I describe in my email below. As anyone got any more
suggestions on what i could do to get this working?
Thanks,
Neil.
> Neil Davies wrote:
> >
> > Hi,
> >
> > I've been asking a number of questions on tclblend. So first of all, thanks for
> > help given already.
> >
> > New question:
> >
> > I'm setting the set tclblend_init to:
> >
> > -Djava.security.policy=$LIB/samples.policy
> >
> > to change the security policy, as before i did this, when i tried to create an
> > object by calling a method i got a security error.
> >
> > The changes seem to be picked up OK. But now, when i try to call the method the
> > tclsh now dies and I get a core dump. The first few lines of the error output
> > look like this:
> >
> > *** panic: symbol "ioctl" undefined
> > SIGABRT 6 abort (generated by abort(3) routine)
> > si_signo [6]: ABRT
> > si_errno [0]:
> > si_code [-1]: SI_LWP [pid: 19060, uid: 19379]
> > stackpointer=FFBE94A0
> >
> >
> > It seems to me that I may have built something incorrectly, but I not sure what.
> > I'm using a Sun work station with solaris, unix.
> >
> > Thanks for any help.
> >
> > Neil.
I've just found this on the java web site:
http://forum.java.sun.com/read/16791418/qAt1jab-R1H4AAANH#LR
Looks like my problem could be with JNI, any opinions?
I'm using version 1.2.6 of java.
Thanks,
Neil.
Well, did you install the Solaris OS patches? This is clearly
a bug in the Solaris JVM. Perhaps and upgrade to a newer version
would fix this. There is nothing much that can be done for a
JVM bug, and since Java is not "open source", you can't go
in a fix it yourself.
By the way, if you want a good laugh, read this:
http://www.infoworld.com/articles/hn/xml/00/10/24/001024hnsunjava.xml
Mo DeJong
Red Hat Inc