Bug#635979: SIGSEGV on /usr/lib/i386-linux-gnu/libGL.so.1
On Fri, Jul 29, 2011 at 17:39:40 -0500, Edgar Antonio Palma de la Cruz wrote:
> Package: libgl1-mesa-glx
> Version: 7.10.3-3
> Severity: important
>
> Hi, I had found that when I run balazar, balazarbrothers or balazar3 on
> a fresh testing install (i386) a SIGSEGV occurs.
>
> Heres my gdb backtracking with python2.6
>
> $ gdb python2.6
> There is NO WARRANTY, to the extent permitted by law. Type "show
> copying" and "show warranty" for details.
> This GDB was configured as "i486-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /usr/bin/python2.6...Reading symbols
> from /usr/lib/debug/usr/bin/python2.6...done. done.
> (gdb) run /usr/games/balazar
> Starting program: /usr/bin/python2.6 /usr/games/balazar
> [Thread debugging using libthread_db enabled]
> * Balazar * Balazar lives in /usr/share/games
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xb73d6bc6 in glGetString () at glapi_x86.S:428
> 428 glapi_x86.S: No existe el fichero o el directorio.
> in glapi_x86.S
> (gdb) bt full
> #0 0xb73d6bc6 in glGetString () at glapi_x86.S:428
> No locals.
> #1 0xb79add30 in ?? () from /usr/lib/pymodules/python2.6/soya/_soya.so
> No symbol table info available.
Sorry for the delayed reply. Is this still an issue?
Cheers,
Julien
Reply to: