tag 186916 help thanks I'm a bit lost here. This is probably a bug in pygame, but it seems impossible to debug. Can anyone with an alpha try to reproduce this bug and find some indication on what needs to be fixed ? Thanks. Le mer 09/04/2003 à 23:53, Falk Hueffner a écrit : > Josselin Mouette <joss@debian.org> writes: > > > Le lun 31/03/2003 à 02:02, Falk Hueffner a écrit : > > > falk@juist:~% solarwolf > > > zsh: segmentation fault solarwolf > > > > Could you please provide a GDB backtrace ? > > Sorry, that doesn't yield anything usable: > > falk@juist:~% gdb /usr/bin/python > GNU gdb 5.3-debian > Copyright 2002 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 "alpha-linux"...(no debugging symbols found)... > (gdb) run /usr/games/solarwolf > Starting program: /usr/bin/python /usr/games/solarwolf > (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 26651)] > > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...Cannot find user-level thread for LWP 26651: generic error > (gdb) bt > Cannot find thread 16384: generic error > (gdb) -- .''`. Josselin Mouette /\./\ : :' : josselin.mouette@ens-lyon.org `. `' joss@debian.org `- Debian GNU/Linux -- The power of freedom
Attachment:
signature.asc
Description: PGP signature