What does "getconf GNU_LIBPTHREAD_VERSION" report? On my altix I see:
% getconf GNU_LIBPTHREAD_VERSION
NPTL 0.60
%
After setting LD_ASSUME_KERNEL to "2.4.19" I see:
% getconf GNU_LIBPTHREAD_VERSION
linuxthreads-0.10
%
It is only when using the NPTL thread library that I see the problem.
Rocky
-----Original Message-----
From: owner-manta@sci.utah.edu [mailto:owner-manta@sci.utah.edu] On Behalf
Of James Bigler
Sent: Wednesday, May 25, 2005 9:05 AM
Cc: manta@sci.utah.edu
Subject: Re: [MANTA] bad exit from bin/manta on Altix
So this is the kernel I'm using (stock from Mandrake 10.0), and I don't
see the errors you report. I'm using a fresh update as well.
Linux muzzle.sci.utah.edu 2.6.3-7mdk-p3-smp-64GB #1 SMP Wed Mar 17
15:34:39 CET 2004 i686 unknown unknown GNU/Linux
Perhaps my kernel isn't new enough?
James
Rocky Rhodes wrote:
It will show up in other linux distributions. Google'ing "nptl
linuxthreads" gave me a bunch of hits including:
http://linuxdevices.com/articles/AT6753699732.html
I had tried older versions of the main trunk and didn't have any luck
isolating a change. I tried versions back to 308 that all failed
similarly,
and version 300 doesn't build for me. It has probably always been this
way
and I just had this environment variable set when I tried it before.
Rocky
-----Original Message-----
From: owner-manta@sci.utah.edu [mailto:owner-manta@sci.utah.edu] On
Behalf
Of James Bigler
Sent: Tuesday, May 24, 2005 7:59 PM
Cc: manta@sci.utah.edu
Subject: Re: [MANTA] bad exit from bin/manta on Altix
You could try checking out an older version and see if it happens.
The Thread_pthread.cc file is pretty hairy. The altix is the only
machine we've had complaints about, though. Should this be showing up
in other modern distributions? What do the SGI docs say about that?
James
Rocky Rhodes wrote:
If I run "bin/manta -bench 10 10 -imagedisplay null -np 2" on an Altix,
the program exits in a bad way, complaining of "ERROR: Incorrect Phase"
and then telling me that "Thread 'idle or main'" got a SIGSEGV. If I
run this again with the LD_ASSUME_KERNEL environment variable set to
"2.4.19" it exits cleanly.
SGI's documentation says that this behavior is indicative of an
application "which depends on behaviors in which the LinuxThreads
implementation deviates from the POSIX standard". The LD_ASSUME_KERNEL
environment variable forces the application to use the old LinuxThreads
implementation rather than NPTL (Native POSIX Thread Library). I think
the new thread package was included with ProPack 3.0 on the Altix. You
might not see this problem on your Altix if it is running an earlier
version of the system software.
I thought I had tried this earlier and didn't have this problem, but as
it is just an environment variable, now I'm wondering if this has
always
been broken this way. Is anyone aware of any changes in the pthread
code made over the last week or so that may have changed this behavior?
Does anyone feel more qualified than I do about mucking around in this
code and trying to understand what goes on when the program exits?
Rocky
Archive powered by MHonArc 2.6.16.