Re: Fatal signal: Segmentation Fault (SDL Parachute Deployed)

[Erik Sigra <sigra at home dot se>]

onsdagen den 14 februari 2001 18:40 skrev Stan Shebs:
> Erik Sigra wrote:
> > I tried the SDL interface and got this:
> >
> > Fatal signal: Segmentation Fault (SDL Parachute Deployed)
>
> That's the generic "something bad happened in SDL" message, there
> are literally dozens of possible reasons for this.  (Current sources
> work for me.)  I suggest running under GDB and looking at the backtrace
> for more info.

I don't know if it helps but here is what I got:

work@a77:~/sourcecode/cvs/xconq/x11 > gdb --exec=sdlconq
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
(gdb) run
Starting program: /home/work/sourcecode/cvs/xconq/x11/sdlconq
[New Thread 1024 (runnable)]
 
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (runnable)]
strcmp (p1=0x0, p2=0x814efdb "dga") at ../sysdeps/generic/strcmp.c:38
38      ../sysdeps/generic/strcmp.c: Filen eller katalogen finns inte.
(gdb) backtrace
#0  strcmp (p1=0x0, p2=0x814efdb "dga") at ../sysdeps/generic/strcmp.c:38
#1  0x804a2ae in ?? ()
#2  0x8049e10 in ?? ()
#3  0x401c4a4e in __libc_start_main (main=0x8049d10, argc=1, argv=0xbffff69c, 
init=0x80495d8, fini=0x814ee14,
    rtld_fini=0x4000aa20 <_dl_fini>, stack_end=0xbffff694) at 
../sysdeps/generic/libc-start.c:92
(gdb)