[Python-modules-team] Bug#454988: python-opengl: Segmentation fault

Michael Krauss hippodriver at gmx.net
Sat Dec 8 15:49:22 UTC 2007


Package: python-opengl
Version: 3.0.0~a6-4
Severity: important

Every time I start this script at 
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/325391
I am getting a segmentation fault without any further error messages.

>From gdb I get the following output:

mickraus at gandalf:~/tmp$ gdb python
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
"/home/mickraus/tmp/graph.py" is not a core dump: File format not
recognized
(gdb) run graph.py
Starting program: /usr/bin/python graph.py
(no debugging symbols found)
warning: no loadable sections found in added symbol-file
system-supplied DSO at 0x7fff205fd000
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x2b988b333cf0 (LWP 5638)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x2b988b333cf0 (LWP 5638)]
0x00002b988c53286e in glGetError () from /usr/lib/libGL.so.1


The same program is running well on a i386 machine with debian etch.

Kind regards,
Michael Krauss

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23.9-slh64-smp-15 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages python-opengl depends on:
ii  freeglut3                     2.4.0-6    OpenGL Utility Toolkit
ii  libgl1-mesa-glx [libgl1]      7.0.2-2    A free implementation of the OpenG
ii  libglu1-mesa [libglu1]        7.0.2-2    The OpenGL utility library (GLU)
ii  python                        2.4.4-6    An interactive high-level object-o
ii  python-central                0.5.15     register and build utility for Pyt
ii  python-ctypes                 1.0.2-2    Python package to create and manip
ii  python-setuptools             0.6c7-1    Python Distutils Enhancements

python-opengl recommends no packages.

-- no debconf information





More information about the Python-modules-team mailing list