Forums » Linux

Segmentation Fault

12»
Jun 20, 2003 Ragnarok link
Ok..I've looked through the posts and cannot find anything that helps.

I'm running Gentoo with FireGL drivers for my Radeon.
When the game starts I can log in, it loads up and allows me to go online/play/etc. However it won't come out of 640x480 and it dies with a SegFault when i try to quit the game.

Anyone have any idea? A few ppl said to edit my config.ini file but it won't create one to edit as it SegFaults before it exits clean.

Just so you know...all my other games seem to work fine so I don't think it's a driver issue.


Help!?!?
Jun 20, 2003 The Kid link
Look on the news page.
Jun 20, 2003 Ragnarok link
Uh...blaster...I looked in the News Section..it says to Edit the "config.ini" file....that's the problem..it's not creating one.
Jun 20, 2003 raybondo link
You can create it yourself if there's not one there.
Create a text file called config.ini with these 3 lines:

[refgl]
doshaders=0
dovertexbuffers=0
Jun 20, 2003 Ragnarok link
Thanks raybondo and blaster for the help..will try that...still getting a seg fault...very strange..hmm..any other ideas?
Jun 20, 2003 raybondo link
Did the bug reporter program come up? If so, please submit a bug report because it automatically has info about where Vendetta crashed.
Jun 20, 2003 Ragnarok link
Unfortunately the bug reporter doesn't come up either...sorry..does it write it to a log file anywhere? I'll send it in.

Jun 20, 2003 raybondo link
It should write info to errors.log
Jun 20, 2003 The Kid link
Ok, just start up vendetta, and press quit before it can seg fault. then that'll create a config.ini.
Jun 20, 2003 Ragnarok link
Here's the error log...sorry..but there's not much here:



[Sat Jun 21 01:01:05 2003] Found driver: "OpenGL Reference GKGL driver". Type 5, Version 19.0. Load @0x0825f758
[Sat Jun 21 01:01:05 2003] Instantiate address: 0x401c0c20
[Sat Jun 21 01:01:05 2003] Found driver: "Open Sound System driver". Type 1, Version 6.1. Load @0x08261610
[Sat Jun 21 01:01:05 2003] Instantiate address: 0x40018d40
Found 0 joystick(s)
osssound: ospace info: fragstotal=8, fragsize=8192
osssound: dspbuf = 0x4a445000
OSS sound initialized: 44100Hz, 16bit stereo, 371ms buffer
Jun 20, 2003 raybondo link
Hmm, I wonder where it's segfaulting then that Vendetta doesn't catch it. Vendetta sets up a bunch of signal handlers and then does a stack trace to the errors.log file. I don't know what would happen to bypass that.
Jun 22, 2003 Ragnarok link
I guess i'll have to wait for a new update...dang :(

Oh well...excellent game otherwise.

Thanks for the help....if anyone comes up with any other ideas pls let me know.

I play ingame as Huntaar.
Jun 22, 2003 Ragnarok link
Ok..I managed to find the trouble with the Seg Fault.

Apparently Vendetta doesn't like having a user with a different group.
My main login is cgeeks but the group is wheel.
I created a new login and it starts with no seg fault now! w00t!!

But a new problem has arisen...now the graphics are all choppy.
It's using the correct driver and i've modified the config.ini file but it runs like i've got a 1mg video card.

The graphics worked great before..but now they don't...God I love Linux!

LOL
Jun 22, 2003 raybondo link
Hmm, maybe it didn't like the other group because Vendetta is installed with the wrong permissions? I'm not sure what they are normally for vendetta. It may not have been able to open some of it's files due to permission problems.

As for the choppyness, if you have a radeon 9500 or above, maybe rglow is on and that could be causing the slow framerate.
/set rglow 0
Oh wait, that gets disabled automatically when doshaders=0.
Hmm. try setting your video setting to Low and see if that helps. Maybe linux is wasting video card memory or something.
Jun 22, 2003 a1k0n link
Well, if changing permissions "fixes" it but makes it slow, then your video drivers probably can't access whatever /dev/radeon_firegl_device because it requires group wheel. I don't see why Vendetta can't catch the crash, though. *shrug* Try running ~/.vendetta/vendetta under gdb and then tracing. (gdb ~/.vendetta/vendetta, then type run, then when it crashes type where and post the result).
Jun 22, 2003 Ragnarok link
Will do that...emerging gdb now.

The slow drivers and permissions was actually my AGP settings in X.
I was looking at the post on the 9700 and double checked my AGP..it was at 4..brought it back to 2 and it works great again!

Except of course for that pesky seg fault.

If it helps...it only faults when I'm changing sectors.?

I'll post the info from gdb as soon as I get it.

Thanks again for all the help.
Jun 23, 2003 Ragnarok link
Here's what happens when I run it in gdb.
I tried last nite running it then using gdb and got the same error when it crashed. At least it was the same library file that caused the crash.

Hope this helps.

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...
Program received signal SIGTRAP, Trace/breakpoint trap.
0x40000b40 in _start () from /lib/ld-linux.so.2
(gdb) where
#0 0x40000b40 in _start () from /lib/ld-linux.so.2
Jun 23, 2003 a1k0n link
Whoa. Does it always die with SIGTRAP instead of SIGSEGV? We don't catch SIGTRAP at all, since we never generate it. I have no idea what's actually going on here. I can only guess that the drivers are either generating SIGTRAP to flag an internal error, or something is just totally screwing up the stack.

Sorry, but I really don't know what we can do about that. You gotta love lunix.
Jun 23, 2003 Ragnarok link
It might have something to do with me running XFree 3.2 and FireGl..they don't always want to get along....GOD I hope ATI comes out with a new driver soon...gonna have to google it to find a better one...sigh.

Thanks for the help all!
Jul 29, 2003 Ragnarok link
Talked to furball on this as he runs gentoo also...trying a new glibc to see if that works...i'll let ya know.