[ut2003io] Anyone Using GLIBC 2.2.5?

[David Hedbor]

"Ryan C. Gordon" <ryan at epicgames.com> writes:

>> I'm a bit concerned about this.. is anyone running the UT2003 Linux
>> client on a system with GLIBC 2.2.5? The game segfaults on the
>> libpthread.so library, which correct me if I'm wrong, comes from GLIBC.
>> GLIBC 2.2.5 is whats used on Mandrake 9.0.
>
> "libpthread" is always the first entry listed when you crash. It has
> to do with the way Linux and ut2003 handle segfaults.
>
> (I _did_ have a glibc incompatibility with a Gentoo user, but it was a
> different sort of problem).
>
> I've had reports of success on Mandrake 9.0.
>
> Is this the crash when trying to create a single player profile.


I think this piece of information will be useful: Mandrake strips the
libpthread library in the glibc package. The result of this bright
move is that the backtrace is invalid. I.e the actual backtrace isn't
shown. Also, when debugging with gdb, threads aren't detected and
things to go hell (not that it matters in this case anyway).

I can post a couple of libs you (hopefully) and put in LD_LIBRARY_PATH
to get the actual crash backtrace. Just say so and I'll put them up
somewhere.

	-- David

P.S. Mandrake stripped libpthread a long time ago. I spent days trying
to figure out why gdb didn't work with my threaded program, trying
various versions of gdb, patches and all kinds of stuff. When I
finally figured it out, I told Mandrake and they stopped their
stripping. However recently, they started stripping again. Check the
'rpm -q --changelog glibc' and look for 'libpthread'... And yes, this
is a huge problem proving that Mandrake ppl are morons. I will try to
get them to fix this problem again, but unfortunately Mandrake 9.0 is
broken.


-- 
[ Below is a random fortune, which is unrelated to the above message. ]
Old mail has arrived.