On Tue, 24 Oct 2000, Dan Wickstrom wrote:
> I've finished the changes that I need to make for making the notifier
> thread safe, and I want to generate a patch against the ajuba contract
> branch, so I checked it out from sourceforge and built it. When I run
> make test, I get an assertion failure. on tsdPtr-initalized. Is this
> branch supposed to be able to run the tests, or do I need to wait for
> other changes? I was hoping that the tests would pass before I made the
> notifier changes, so that I could at least tell if the new notifier
> changes would break anything.
>
> I'm running with the following:
>
> redhat 6.2
> tcl8.3.2
> tcljava from souceforge ajuba contract branch
> blackdown jdk1.1.8_v1
That really should work, everything you are using is
the same as my install except I have the CVS version of Tcl.
When I run the "make test" on the contract
branch, it works just fine. Of course, I am using
IBM JDK 1.3. not the blackdown one. I know there
is a problem with a core dump during some of the
classloader tests when run with JDK 1.1.8 from
blackdown, but you never hit that assert. The
assertion is raised in the case where a JNI function
is called in a thread before the thread local class
cache and JNI thread attach have been done.
... (Time passes) ...
I just tried it with JDK 1.1.8 and now I am getting
a SIGILL in some pthreads code. Very strange.
#0 0xbfffa6ee in ?? ()
#1 0x400dbe05 in pthread_handle_sigrestart (sig=32, ctx={gs = 0, __gsh =
0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 0, edi = 0,
esi = 3221211404, ebp = 3221211844, esp = 3221211372, ebx = 3221211404,
edx = 1074683196, ecx = 0, eax = 0, trapno = 1, err = 0, eip =
1075407969, cs = 35, __csh = 0, eflags = 2097734, esp_at_signal =
3221211372, ss = 43, __ssh = 0, fpstate = 0xbfffc870, oldmask = 4, cr2 =
0}) at pthread.c:636
#2 <signal handler called>
#3 0x40196c61 in __libc_nanosleep () from /lib/libc.so.6
#4 0x400d8fee in pthread_cond_timedwait_relative_new (cond=0x8164d38,
mutex=0x804a0b0, abstime=0xbfffcaf8) at condvar.c:318
#5 0x400d9211 in pthread_cond_timedwait (cond=0x8164d38,
mutex=0x804a0b0, abstime=0xbfffcaf8) at condvar.c:381
#6 0x400b3190 in Tcl_ConditionWait (condPtr=0x804a0a0,
mutexPtr=0x400c92ac, timePtr=0x8049d38) at
/home/mo/project/tcl/unix/../unix/tclUnixThrd.c:686
#7 0x400b3ccc in Tcl_WaitForEvent (timePtr=0x8049d38) at
/home/mo/project/tcl/unix/../unix/tclUnixNotfy.c:742
#8 0x4008e090 in Tcl_DoOneEvent (flags=-3) at
/home/mo/project/tcl/unix/../generic/tclNotify.c:889
#9 0x40061949 in Tcl_VwaitObjCmd (clientData=0x0, interp=0x804de48,
objc=2, objv=0xbfffcc38) at
/home/mo/project/tcl/unix/../generic/tclEvent.c:960
Since I do not see this is the IBM JDK, I am going to
assume that it is a JDK 1.1.8 bug. I hear there is
also a new JDK 1.2 and JDK 1.3 from blackdown, but
I have not downloaded those for testing.
Mo DeJong
Red Hat Inc
----------------------------------------------------------------
The TclJava mailing list is sponsored by Scriptics Corporation.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
An archive is available at http://www.mail-archive.com/tcljava@scriptics.com
