I have been trying to get warzone running for days without any luck.
I always receive the same error after starting the game it crashes before the menu comes up the error i get is
No function contains program counter for selected frame.
Saved dump file to '/tmp/warzone2100.gdmp-MLDQVD'
If you create a bugreport regarding this crash, please include this file.
Segmentation fault
Here is the dump file
http://pastebin.com/m7514ef
I am running Slackware 12.2 with a nvidia fx5200 with the latest drivers. I have downgraded Phyfs to 1.0.1 and OpenAL to 1.4 but still have the same problem.
I have just tried installing version 2.0.5 and 2.0.10 and they seem to work fine but 2.1.0 and above fail including trunk.
Not sure Where to go from here
sav
Segmentation fault at startup
-
cybersphinx
- Inactive

- Posts: 1695
- Joined: 01 Sep 2006, 19:17
Re: Segmentation fault at startup
From the crashdump it looks like the error is in libGLC or libfreetype, not Warzone itself. I think you have compiled your programs with -fomit-framepointers, if you could recompile libfreetype, libGLC and Warzone without that (and without stripping), the crashdump might be more useful.
-
savo
- Greenhorn
- Posts: 6
- Joined: 10 Jun 2009, 17:13
Re: Segmentation fault at startup
Ok i will give that ago tonight if i get time and post my results when i am done.
Thanks for the fast reply
sav
Thanks for the fast reply
sav
-
savo
- Greenhorn
- Posts: 6
- Joined: 10 Jun 2009, 17:13
Re: Segmentation fault at startup
I have just had a look and neither package was compiled with fomit-framepointers here is what they was configured with
queslgc
CFLAGS="$SLKCFLAGS" \
./configure \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--docdir=/usr/doc/$PRGNAM-$VERSION \
--enable-data=yes \
--disable-executables \
--build=$ARCH-slackware-linux
./configure \
--prefix=/usr \
--mandir=/usr/man \
--with-x \
--with-freetype-src=$CWD/freetype-2.3.7 \
--with-freetype-bytecode=$ENABLE_BCINT \
--with-devicetables \
--enable-libff \
--enable-pyextension \
--enable-type3 \
--enable-tilepath \
--disable-debug \
--enable-static=no \
--enable-shared=yes \
--build=$ARCH-slackware-linux
queslgc
CFLAGS="$SLKCFLAGS" \
./configure \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--docdir=/usr/doc/$PRGNAM-$VERSION \
--enable-data=yes \
--disable-executables \
--build=$ARCH-slackware-linux
./configure \
--prefix=/usr \
--mandir=/usr/man \
--with-x \
--with-freetype-src=$CWD/freetype-2.3.7 \
--with-freetype-bytecode=$ENABLE_BCINT \
--with-devicetables \
--enable-libff \
--enable-pyextension \
--enable-type3 \
--enable-tilepath \
--disable-debug \
--enable-static=no \
--enable-shared=yes \
--build=$ARCH-slackware-linux
-
cybersphinx
- Inactive

- Posts: 1695
- Joined: 01 Sep 2006, 19:17
Re: Segmentation fault at startup
The configure options don't tell me anything about your compiler options (and -fomit-frame-pointer is a compiler option). In the first, $SLKCFLAGS is unknown, and the second seems to use whatever CFLAGS are default.
-
savo
- Greenhorn
- Posts: 6
- Joined: 10 Jun 2009, 17:13
Re: Segmentation fault at startup
I have now reinstalled everything and still have the same problem.and the log looks the same to me http://pastebin.com/m159c84cc
The versions i installed are
freetype 2.3.7
physfc 1.1.1
OpenAL 1.8.466
quesoglc 0.7.2
warzone trunk
The versions i installed are
freetype 2.3.7
physfc 1.1.1
OpenAL 1.8.466
quesoglc 0.7.2
warzone trunk
-
savo
- Greenhorn
- Posts: 6
- Joined: 10 Jun 2009, 17:13
Re: Segmentation fault at startup
I found someone having the same problem and there fix for it here
http://developer.wz2100.net/ticket/106
Which worked for me as well
Thanks for your help.
http://developer.wz2100.net/ticket/106
Which worked for me as well
Thanks for your help.
-
Buginator
- Professional

- Posts: 3285
- Joined: 04 Nov 2007, 02:20
Re: Segmentation fault at startup
And that 'fix' is, not to use a broken compilersavo wrote:I found someone having the same problem and there fix for it here
http://developer.wz2100.net/ticket/106
Which worked for me as well
Thanks for your help.
Figured out how to work around this bug. It is being caused by some kind of bug in gcc shipped in slackware 12.2 - simply recompiling the same version of freetype with the freetype.Slackbuild changed from:
elif [ "$ARCH" = "i486" ]; then
SLKCFLAGS="-O2 -march=i486 -mtune=i686"
to
elif [ "$ARCH" = "i486" ]; then
SLKCFLAGS="-O2"
and using upgradepkg --reinstall on the package created in /tmp makes this problem go away.
and it ends here.