Bug 206532 – dev-python/pyopengl-2.0.1.09-r1 dumps core on help("modules")

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Santiago Gala 2008-01-18 15:17:15 UTC]

$ gdb /usr/bin/pythonGNU gdb 6.7.1
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-pc-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/python 
(no debugging symbols found)
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x2b93f92c4000
(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)
Python 2.5.1 (r251:54863, Jan 18 2008, 12:07:12) 
[GCC 4.2.2 (Gentoo 4.2.2 p1.0)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
>>> help("modules")
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Please wait a moment while I gather a list of all available modules...

(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)
(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)
(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)
(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)
(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)
(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)
(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)
(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)
(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.
0x00002aaaaaab8de1 in Togl_Init ()
   from /usr/lib64/python2.5/site-packages/OpenGL/Tk/linux2-tk8.4/Togl.so
(gdb) quit
The program is running.  Exit anyway? (y or n) y
sgala@marlow ~/newcode/python3k $ equery belongs /usr/lib64/python2.5/site-packages/OpenGL/Tk/linux2-tk8.4/Togl.so
[ Searching for file(s) /usr/lib64/python2.5/site-packages/OpenGL/Tk/linux2-tk8.4/Togl.so in *... ]
dev-python/pyopengl-2.0.1.09-r1 (/usr/lib64/python2.5/site-packages/OpenGL/Tk/linux2-tk8.4/Togl.so)


Reproducible: Always

Steps to Reproduce:
1. see above
2.
3.

Actual Results:  
core dump

Expected Results:  
documentation (empty or not)

I guess it is related with a warning about the swig version that pyopengl gives on emerging, or even against gcc version. Still, dumping core on a request for help is not acceptable behavior.

[Comment 1 Jakub Moc (RETIRED) 2008-01-18 15:22:01 UTC]

Please review the following and reopen with a useful backtrace and emerge --info output. Thanks.

http://www.gentoo.org/proj/en/qa/backtraces.xml

[Comment 2 Santiago Gala 2008-01-20 13:02:18 UTC]

bug 133602 already shows the behavior I'm having trouble with and it has rested unacted for half a year.

I don't think I should reemerge half of my system just to have the same response at the end

[Comment 3 Jakub Moc (RETIRED) 2008-01-20 13:04:27 UTC]

(In reply to comment #2)
> bug 133602 already shows the behavior I'm having trouble with and it has rested
> unacted for half a year.

Hmmmm? How's exactly some swig warning related to this crash?