problems with ldd/pthreads?
Hi, I had some problems with quake 3 crashing when changing videomodes,
until I found this in the NVIDIA readme:
"Q: OpenGL applications crash and print out the following warning:
WARNING: Your system is running with a buggy dynamic loader.
This may cause crashes in certain applications. If you
experience crashes you can try setting the environment
variable __GL_SINGLE_THREADED. For more information please
consult the FREQUENTLY ASKED QUESTIONS section in the file
/usr/share/doc/NVIDIA_GLX-1.0/README.
A: The dynamic loader on your system has a bug which will cause
applications linked with pthreads, and that dlopen() libGL multiple
times, to crash. This bug is present in older versions of the dynamic
loader. Distributions that shipped with this loader include but
are not limited to RedHat Linux 6.2 and Mandrake Linux 7.1. Version
2.2 and later of the dynamic loader are known to work properly. If
the crashing application is single threaded then setting the environment
variable __GL_SINGLE_THREADED to any value will prevent the crash.
In the bash shell you would enter
export __GL_SINGLE_THREADED
and in csh and derivatives use
setenv __GL_SINGLE_THREADED
Previous releases of the NVIDIA Accelerated Linux Driver Set attempted
to work around this problem, however the workaround caused problems with
other applications and was removed after version 1.0-1541.
Q: When I run Quake3, it crashes when changing video modes; what's wrong?
A: You are probably experiencing the problem described above. Please
check the text output for the "WARNING" message describe in the
previous hint. Setting __GL_SINGLE_THREADED as described above,
before running Quake3 will fix the problem."
Now this does work to solve the problem but since ldd is version 2.3.x
I don't think this is the problem, or at least the problem is somewhere
else. Every time I tried to change resolution the program got a signal
11 (but X still changed resolutions). There is also something strange
going on when trying to launch ut 2003 which seems to suffer from the same
problem when trying to change the resolution on startup. (output is much
less descriptive though).
I guess it might have something to do with my kernel since I'm only running
2.2, but I'm confused as to what would be the cause?
any thoughts would be much appreciated,
wim
--
Only two things are infinite: human stupidity and the universe, and I'm not sure about the latter.
-- Albert Einstein
Reply to: