After running Valgrind it seems that python-opengl package is to blame. Here is
the Valgrind trace in question (the whole log is attached):
------------------------------------------------------
==7211== Process terminating with default action of signal 11 (SIGSEGV)
==7211== Access not within mapped region at address 0x8C8
==7211== at 0x1117b044: Togl_Init (in
/usr/lib/python2.5/site-packages/OpenGL/Tk/linux2-tk8.4/Togl.so)
==7211== by 0x0ca54885: Tcl_LoadObjCmd (in /usr/lib/libtcl8.4.so.0)
...
-------------------------------------------------------
help("modules") perhaps tries to import all the modules and some of the
module binaries are not behaving correctly...
After removing python-opengl (and python-qt3-gl and python-qt4-gl as
dependencies) an error in the next 'misbehaving' package showed up:
-----------------------------------------------------------------------------------------
>>> help("modules")
Please wait a moment while I gather a list of all available modules...
terminate called after throwing an instance of
'Synopsis::Python::Object::TypeError'
what(): a new-style class can't have only classic bases
Aborted
------------------------------------------------------------------------------------------
It seems that the individual python packages are to blame or the way
python implements help('modules'). Either way this is not as critical as
I thought.
** Tags removed: 64bit
** Attachment added: "Valgrind log"
http://librarian.launchpad.net/5835269/valgrind.log
--
Feisty, Python2.5, x86_64, help("modules") => Segfault
https://launchpad.net/bugs/80656
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
