from PyQt4 import Qwt5 - produces a segfault in sip.so

Bug #962313 reported by Ben Reynwar
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python2.7 (Ubuntu)
New
Medium
Unassigned

Bug Description

>>> from PyQt4 import Qwt5

Program received signal SIGSEGV, Segmentation fault.
Python Exception <class 'gdb.error'> There is no member named ma_mask.:
createClassType (client=0xb78b30b8, ctd=0xb78c080c, mod_dict=) at /build/buildd/sip4-4.13.2/siplib/siplib.c:5502
5502 /build/buildd/sip4-4.13.2/siplib/siplib.c: No such file or directory.
(gdb) backtrace
Python Exception <class 'gdb.error'> There is no member named ma_mask.:
#0 createClassType (client=0xb78b30b8, ctd=0xb78c080c, mod_dict=) at /build/buildd/sip4-4.13.2/siplib/siplib.c:5502
Python Exception <class 'gdb.error'> There is no member named ma_mask.:
#1 0xb77026b4 in sip_api_init_module (client=0xb78b30b8, mod_dict=) at /build/buildd/sip4-4.13.2/siplib/siplib.c:1418
#2 0xb7743bde in initQwt () from /usr/lib/python2.7/dist-packages/PyQt4/Qwt5/Qwt.so
#3 0x081231b7 in _PyImport_LoadDynamicModule ()
#4 0x0806dad3 in load_module.39170 ()
#5 0x0806dd74 in import_submodule.39181 ()
#6 0x080b4b66 in load_next.39186 ()
#7 0x0806e686 in import_module_level.isra.3.39207 ()
#8 0x0812ce4e in builtin___import__.32839 ()
#9 0x08149aff in PyObject_Call ()
#10 0x0814dab9 in PyEval_CallObjectWithKeywords ()
#11 0x08158fa5 in PyEval_EvalFrameEx ()
#12 0x081842f0 in PyEval_EvalCodeEx ()
#13 0x08184e83 in PyImport_ExecCodeModuleEx ()
#14 0x0806d3e0 in load_source_module.39127 ()
#15 0x08195e02 in load_package.39220 ()
#16 0x0806dd74 in import_submodule.39181 ()
#17 0x0806e2df in ensure_fromlist.part.7 ()
#18 0x0806e71d in import_module_level.isra.3.39207 ()
#19 0x0812ce4e in builtin___import__.32839 ()
#20 0x08149aff in PyObject_Call ()
#21 0x0814dab9 in PyEval_CallObjectWithKeywords ()
#22 0x08158fa5 in PyEval_EvalFrameEx ()
#23 0x081842f0 in PyEval_EvalCodeEx ()
#24 0x08185ab8 in PyRun_InteractiveOneFlags ()
#25 0x08185def in PyRun_InteractiveLoopFlags ()
#26 0x081956be in PyRun_AnyFileExFlags ()
#27 0x08198cf9 in Py_Main ()
#28 0x0805e93b in main ()
(gdb)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: python2.7-minimal 2.7.3~rc2-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.31-generic-pae 3.2.12
Uname: Linux 3.2.0-19-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Thu Mar 22 09:10:35 2012
ExecutablePath: /usr/bin/python2.7
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: python
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb6fd43ba: addl $0x1,(%eax)
 PC (0xb6fd43ba) ok
 source "$0x1" ok
 destination "(%eax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
 ?? () from /usr/lib/python2.7/dist-packages/sip.so
 ?? () from /usr/lib/python2.7/dist-packages/sip.so
 initQwt () from /usr/lib/python2.7/dist-packages/PyQt4/Qwt5/Qwt.so
 _PyImport_LoadDynamicModule ()
 ?? ()
Title: python2.7 crashed with SIGSEGV in initQwt()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Ben Reynwar (ben-reynwar) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 createClassType (client=0xb6c890b8, ctd=0xb6c9680c, mod_dict=Traceback (most recent call last):
 sip_api_init_module (client=0xb6c890b8, mod_dict=Traceback (most recent call last):
 initQwt () at tmp-qwt5qt4/sipQwtcmodule.cpp:3583
 _PyImport_LoadDynamicModule ()
 load_module.39170 ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in python2.7 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Ben Reynwar (ben-reynwar) wrote :

This bug is no longer present.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.