View Full Version : Linux client segmentation faults
hollywoodb
21st March 2004, 00:10
I just installed the linux client today, I made a script to launch it as it says in one of these posts....
It keep segfaulting, I've never gotten past the screen where I can login or click create character. It usually segfaults right when I click the create character button.
I don't have a segfault problem with any other apps on my system, any idea what would cause this? if more info is needed, just tell me what to post.
Guido
23rd March 2004, 05:36
I hate segfaults, I think they are equivalent to the blue screen of death on windows.
I never get a good error report on why it segfaulted, it just looks like segfault is some form of generic error due to a memory overflow, well that tells me a lot.
Anyway, I sympathise with your plight, perhaps posting your Linux details might spur someone into finding a solution for you.
Pluribus
23rd March 2004, 06:22
There are several things that cause segfaults :-)
In the case of Hollywoodb, he ran memtest86 and found that he had bad RAM. Hopefully fixing that will fix the client. (The game is a memory pig)
My latest fun is that there is combination of glibc and newer kernels that break old linux threads. Alas, this breaks the client, however there is a workaroud in that case... (You know it by an INSTANT Segmentation fault before it even gives the "server selection menus")
LD_ASSUME_KERNEL=2.4.1 ./elaunch
NOTE: I have a survey up for linux users about thier distros... if NOONE answers that thier distro is GCC 2.x based, then I can upgrade my build distro to a GCC 3.x build environment.
which will make my life so much nicer.
Solalique
23rd March 2004, 19:58
I hope this works out (gcc3). :)
I am at an ISV ... while we still maintain our older builds, when we rebuilt everything on 2.4-nptl gcc3 for RHAS 3.0 support, it cut the footprint on disk (compared to older linux builds) to about 1/3 the original size, and CPU/RSS consumption is, I'd say, very roughly 25% less.
Naturally this will vary greatly with the type application, but moving forward is a good thing.
Pluribus
23rd March 2004, 22:32
I would LOVE to make the move to GCC, alas, my biggest issue is that the client is about 90% C++ code. Which means that I cant support GCC 2.9x based distro with GCC 3.x compiled code. GCC 3.x version is larger, however, the code is much more stable and the exception handling actually WORKS....
I need to talk to Teppy and see if he will release the player names of the people using the GCC 2.9x based distros and find out WHY they havent updated... (Considering the cost :-) )
hollywoodb
25th March 2004, 00:14
well, new memory, badblocks found 0 bad blocks, filesystem is in order, everything runs perfect, atitd linux client still segfaults.... the LD_ASSUME_etc etc didn't help either.... I really don't know what's causing this, I've never had a segfault problem before (until the ram went bad, but now I've got good new corsair).
Pluribus
25th March 2004, 05:17
Lets try a few things....
glxdiag | grep -i Direct
if output says Direct Rendering: No , then fix your NVIDIA driver install
then do a
ls -l /usr/lib/libGL*
and post the output here....
lrwxrwxrwx 1 root root 21 Mar 24 15:34 /usr/lib/libGLcore.so.1 -> libGLcore.so.1.0.5336
-rwxr-xr-x 1 root root 4913084 Mar 24 15:34 /usr/lib/libGLcore.so.1.0.5336
-rw-r--r-- 1 root root 653 Mar 24 15:34 /usr/lib/libGL.la
lrwxrwxrwx 1 root root 10 Mar 24 15:34 /usr/lib/libGL.so -> libGL.so.1
lrwxrwxrwx 1 root root 17 Mar 24 15:34 /usr/lib/libGL.so.1 -> libGL.so.1.0.5336
-rwxr-xr-x 1 root root 367092 Mar 24 15:34 /usr/lib/libGL.so.1.0.5336
I BELIEVE that you said you were using Gentoo, so make sure that you have emerge'd the compat package.
Altean
28th March 2004, 21:37
just FYI, anyone using debian stable(woody) is using a 2.XX based distro.
vBulletin v3.0.5, Copyright ©2000-2008, Jelsoft Enterprises Ltd.