games-strategy/scorched3d-36.2 segfaults for me. I had one other person try for me but it worked for them. I tried running it as a normal user, and also as root. The reason I tried as root is that when run as a normal user it complains: Scorched3D - Version 36.2 (ae) : Warning: Your display settings file (/usr/share/games/scorched3d/data/display.xml) cannot be written to. Your settings will not be saved from one game to the next. To fix this problem correct the permissions for all the files in the /usr/share/games/scorched3d/data directory. I will attach an strace log. Portage 2.0.49-r18 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.6.1) ================================================================= System uname: 2.6.1 i686 AMD Athlon(TM) XP 1800+ Gentoo Base System version 1.4.3.10p1 distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -funroll-loops -fprefetch-loop-arrays -pipe -mmmx -msse -m3dnow -mfpmath=sse,387" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -funroll-loops -fprefetch-loop-arrays -pipe -mmmx -msse -m3dnow -mfpmath=sse,387" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache notitles sandbox" GENTOO_MIRRORS="http://gentoo.noved.org/ http://mirrors.tds.net/gentoo http://cudlug.cudenver.edu/gentoo/ http://mirror.tucdemonic.org/gentoo/ http://www.gtlib.cc.gatech.edu/pub/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="3dnow X aalib alsa apm avi berkdb cdr crypt cups dv encode foomaticdb gdbm gif gnome gpm gtk gtk2 imlib java jpeg kde ldap libg++ libwww mad mikmod mmx motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell sse ssl svga tcltk tcpd tiff truetype x86 xml2 xmms xv zlib"
Of course I did forget something. The segfault occurs after doing this: 1) starting scorch3d as a normal user 2) selecting Start a single or multi-player game (the upper most option) 3) start an easy single player game 4) select a tank, name, and hit OK strace following soon.
Created attachment 23944 [details] schorched3d strace log (trimmed from 44,000+ lines to 20,000)
a gdb back trace would probably be more helpful ...
It's been a while since I did one of those, with some basic instructions I'll go ahead and do that if you'd be so kind.
Well I'll give this a shot anyway, I pulled it up with gdb-6.0 via gdb scorched3d and then told it "run", got to the usual spot and it outputted: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 9798)] 0x41610e7d in s10500 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so I looked to see if the ebuild supported the debug USE flag but does not appear to. Did I do this right, and if so, is there something more I can do to give more useful data?
Try the backtrace command in gdb once you get the segfault.
Thanks for the tip and patience. I tried to recompile with debugging support, but the ebuild doesn't listen to the debug USE flag. Someone gave me a tip, RESTRICT="nostrip" emerge scorched3d. This is the result after doing so: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 9580)] 0x41610e7a in s10500 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so (gdb) backtrace #0 0x41610e7a in s10500 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so Cannot access memory at address 0xbf7ffff8 (gdb) Anything else I can do?
What version of xfree and what are you using for your opengl?
x11-base/xfree-4.3.0-r3 Oddly emerge -p opengl outputs the same information, but I don't think I'm answering that question right. I'm using an ATI Radeon 9000 Pro 64MB video card. As far as the drivers go, media-video/ati-drivers-3.2.8 Something odd that I just noticed is that I once had ati-drivers-3.7.0 installed. I had problems with them such as the machine hard locking many times a day, where before it was not. So i went back to 3.2.8. However, emerge -s ati-drivers shows: * media-video/ati-drivers Latest version available: 3.2.8 Latest version installed: 3.7.0 So I'm not sure what's going on there.
try this: emerge -C ati-drivers emerge =ati-drivers-3.2.8 restart X if it still crashes, try running `opengl-update xfree` and restarting X and then see if it works ...
Okay, I did those items. First time around after removing ati-drivers and installing 3.2.8 and entering xfree, I still got the problem. So i dropped out of xfree, did an opengl-update xfree, tried again, and still got the problem. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 21014)] 0x41608e7b in s10500 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so (gdb) backtrace #0 0x41608e7b in s10500 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so
Tried some more, and had something different happen. After selecting a tank or whatever and hitting okay I then had my mouse out of the window of the game. I heard what sounded like a gunshot. I looked at gdb, and it hadn't complained. I went to move the mouse back into the window, and as soon as the mouse entered it, gdb output this, and then I did a backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 23014)] 0x41609681 in s10500 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so (gdb) backtrace #0 0x41609681 in s10500 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so #1 0x00001bfc in ?? () #2 0x00001bfc in ?? () #3 0x4628a040 in ?? () #4 0x462946c4 in ?? ()
More tinkering. Inside the game there is an option to disable GL extensions : "No GL Extensions". I used this, and the game is firing up just fine now. Still looks very good as well. What do you think I should do next, try to find out more or close the bug?
i dont know much (or anything) about ati drivers since all i use is nvidia ... *could* be a bug in that ati dri module with opengl :/ how about put a warning to ati users in the ebuild and call it a day ?
Works for me. Generally I've found the ati drivers to be very buggy. Warning would be fine.
ok, added warning to cvs if user has 'ati-drivers' emerged
