Hi,
I am not sure if this is the cuase of your problem, but the natiuve_threads
jdk uses the signals to communicate between threads including SIGUSR1,
SIGUSR2 (used by linuxthreads), SIGSTOP, SIGCONT (used to stop threads to
allow garbage collection thread to run, and SIGUNUSED which is used by
threads to interrupt one another (to allow java interrupts).
So there is alot of signal activity going on in the native_threads port.
Also note, the java thread stack dump may not be reporting signal names
(numbers) properly so what you are seeing might really be one of these
signals.
I hope this info helps.
Please let me know if you need more info.
Kevin
Blackdown Porting Team (for PPC).
----------------------------------------------------------
Kevin B. Hendricks
Associate Professor, Operations & Information Technology
School of Business, College of William & Mary
Williamsburg, VA 23187, [EMAIL PROTECTED]
http://business.tyler.wm.edu
