Bug 71693 – Segmentation Fault (SDL Parachute Deployed)

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description David Backeberg 2004-11-18 12:53:22 UTC]

I get crashes involving the following message:
Segmentation Fault (SDL Parachute Deployed)
for the following games:
tuxracer
supertux
fish-fillet

Methinks this is a problem with SDL, but I don't know how best to investigate

Reproducible: Always
Steps to Reproduce:
1.emerge tuxracer supertux fish-fillet
2.try running each of the games
3.they all crash, specifically:

bash-2.05b$ tuxracer
Tux Racer 0.61 -- a Sunspire Studios Production (http://www.sunspirestudios.com)
(c) 1999-2000 Jasmin F. Patry <[e-mail]>
"Tux Racer" is a trademark of Jasmin F. Patry
Tux Racer comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions.
See http://www.gnu.org/copyleft/gpl.html for details.

Fatal signal: Segmentation Fault (SDL Parachute Deployed)

bash-2.05b$ supertux
Datadir: /usr/share/games/supertux
Fatal signal: Segmentation Fault (SDL Parachute Deployed)

bash-2.05b$ fillets
Fatal signal: Segmentation Fault (SDL Parachute Deployed)


Actual Results:  
Games never actually start up. 

Expected Results:  
Games should start up, allowing play. 

emerge info 
Portage 2.0.51-r3 (default-linux/x86/2004.2, gcc-3.3.4, 
glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r1 i686) 
================================================================= 
System uname: 2.6.9-gentoo-r1 i686 AMD Athlon(TM) XP 2000+ 
Gentoo Base System version 1.4.16 
Autoconf: sys-devel/autoconf-2.59-r5 
Automake: sys-devel/automake-1.8.5-r1 
Binutils: sys-devel/binutils-2.14.90.0.8-r1 
Headers:  sys-kernel/linux-headers-2.4.21-r1 
Libtools: sys-devel/libtool-1.5.2-r5 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-march=athlon-xp -O3 -pipe -funroll-loops -fomit-frame-pointer 
-fexpensive-optimizations -ffast-math -frerun-loop-opt" 
CHOST="i686-pc-linux-gnu" 
COMPILER="" 
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /var/qmail/control" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" 
CXXFLAGS="-march=athlon-xp -O3 -pipe -funroll-loops -fomit-frame-pointer 
-fexpensive-optimizations -ffast-math -frerun-loop-opt" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" 
GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo" 
MAKEOPTS="-j2" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="" 
SYNC="rsync://rsync.gentoo.org/gentoo-portage" 
USE="3dnow X aalib acpi alsa apm arts avi berkdb bitmap-fonts cdr crypt cups 
doc dvd dvdr encode esd ethereal f77 fam foomaticdb fortran gdbm gif gnome gpm 
gtkgtk2 imap imlib jack java jikes jpeg kde lcms ldap libg++ libwww mad 
maildir mbox mikmod mmx motif mozilla mpeg mpi mysql ncurses nls obdc 
oggvorbis opengl osspam pdflib perl png ppds python qt quicktime readline 
samba scanner sdl slang snmp spell sse ssl svga tcltk tcpd tiff truetype usb 
videos wmf wxwindows x86 xml2 xmms xv zlib"

[Comment 1 Mr. Bones. (RETIRED) 2004-11-18 21:09:26 UTC]

try remerging all the sdl stuff on your system and the games with CFLAGS="-pipe".
If that fixes things for you, try to isolate which package and cflags are causing the problem.  Reopen this bug with more information after you've tried that.

[Comment 2 David Backeberg 2004-11-19 06:16:52 UTC]

Changed CFLAGS to nothing but -pipe. Wiped all USE flags, except for USE="X gtk gnome -alsa". Still same crashes. 

Tried it with USE="" and CFLAGS="". 

emerge sdl-gfx sdl-image sdl-mixer sdl-net sdl-sound sdl-ttf tuxracer supertux fish-fillets

Everything still crashes on startup, just like before. Should I re-emerge some packages lower down the build chain? What packages should I try reemerging?

[Comment 3 Mr. Bones. (RETIRED) 2004-12-06 14:14:10 UTC]

What's the output of the command "groups" ?

[Comment 4 Mr. Bones. (RETIRED) 2004-12-09 01:48:09 UTC]

reopen with more information.

[Comment 5 David Backeberg 2004-12-22 14:56:58 UTC]

Okay discovered the problem. I hadn't setup ALSA drivers properly. I ran alsaconf, which failed due to the lack of /etc/alsa, then did "touch /etc/alsa", then ran alsoconf again, setup my soundcard. Now everything works fine, no more complaints about the old SDL parachute. I wish there would be a more meaningful error message, like "no sound device found. Do you need to configure your sound device?" The message about "SDL parachute deployed" certainly doesn't help track down the real problem.

[Comment 6 Mr. Bones. (RETIRED) 2011-09-14 20:39:24 UTC]

clean up bug list after bugzilla update