Hi Nicole,

{ ...
{ I upgraded my kernel to version 2.6, and now it looks like these signals
{ aren't being caught anymore -- sort of.
{ ...
{ I've been using blackdown 1.3.1, but as a test I switched to Sun's
{ 1.3.1_10 and am still having the same problem.
{ ...
{ I assumed the problem is related to NPTL, so I have set the
{ LD_ASSUME_KERNEL variable to both "2.2.5" and "2.4.1" to no avail. I
{ thought perhaps I needed to upgrade my libc6, but I don't know that that
{ is the case. Right now it's running 2.2.5-11.5.
{ 
{ Any ideas ? I'll try anything at this point, I'd really like to keep my
{ kernel. Even if I just have the answer and decide to stick with 2.4 for
{ now, I'd at least like to know :o)

Sebastien and my-self are involved in improving the stability of NPTL,
and we plan to provide a trace mechanism for NPTL.
So we are very interested in understanding and trying to fix your
problem that seems not to be related to a JVM.
We have been said that some signals are lost by NPTL.
Using old LinuxThreads (LD_ASSUME_KERNEL) did not fix your problem,
probably because LinuxThreads was also known to loose signals ...
Or maybe the problem is in the kernel ...

Would it be possible for you to extract the code that produces the
problem and provide a very small program we could use in our labs
in order to reproduce the problem with our environment (RedHat 9,
last 2.6 kernel version, last NPTL version) ?


Thanks,

Amicalement/Regards,

Tony Reix

                            Carpe Diem

********************************************************************************
Name:           Tony Reix
Company:        Bull SA : AIX/Linux R&D
EMail:          [EMAIL PROTECTED]
Web-Site:       http://www-frec.bull.com
Address:        BULL, 1 rue de Provence, BP 208, 38432 Echirolles Cedex, France
Phone           04 76 29 72 67 (France), 33 4 76 29 72 67
Fax:            04 76 29 76 00 (France), 33 4 76 29 76 00
Bull Phone:     229-7267
Bull Address:   FREC B1-204             Office: B1-183
********************************************************************************


----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to