python-qwt5-qt4 segfaults immediately in saucy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyqwt5 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Saucy |
Fix Released
|
Medium
|
Brian Murray | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
python-qwt5-qt4 segfaults directly after the first Qwt object is created.
Recreate with:
import PyQt4.Qwt5 as Qwt
k = Qwt.QwtKnob()
or run one of the example programs in /usr/share/
Backtrace:
Program received signal SIGSEGV, Segmentation fault.
0xb623805f in qpycore_
(gdb) bt
#0 0xb623805f in qpycore_
#1 0xb7fc783d in add_lazy_attrs (td=0xb797b3e0) at /build/
#2 add_all_lazy_attrs (td=0xb797b3e0) at /build/
#3 0xb7fc7cac in sipSimpleWrappe
#4 0x081413fe in type_call.25511 (type=0x853641c, args=0xb7d3602c, kwds=0x0) at ../Objects/
#5 0x080c1e45 in PyObject_Call (kw=0x0, arg=0xb7d3602c, func=0x853641c) at ../Objects/
#6 do_call (nk=0, na=<optimized out>, pp_stack=
#7 call_function (oparg=<optimized out>, pp_stack=
#8 PyEval_EvalFrameEx (f=f@entry=
#9 0x080c8702 in PyEval_EvalCodeEx (co=0xb7cc8a88, globals=0xb7d66714, locals=0xb7d66714, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at ../Python/
#10 0x081aed77 in PyEval_EvalCode (co=0xb7cc8a88, globals=0xb7d66714, locals=0xb7d66714) at ../Python/
#11 0x080a9be7 in run_mod (mod=<optimized out>, filename=<optimized out>, globals=0xb7d66714, locals=0xb7d66714, flags=0xbffff01c, arena=0x836ff88) at ../Python/
#12 0x080aa4fd in PyRun_FileExFlags (fp=fp@
closeit=
#13 0x080aadc0 in PyRun_SimpleFil
#14 0x080aaeb3 in PyRun_AnyFileEx
at ../Python/
#15 0x080abb1d in Py_Main (argc=argc@entry=2, argv=argv@
#16 0x080abbfc in main (argc=2, argv=0xbffff154) at ../Modules/
olaf@pc:~$ lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
olaf@pc:~$ apt-cache policy python-qwt5-qt4
python-qwt5-qt4:
Installed: 5.2.1~cvs200911
Candidate: 5.2.1~cvs200911
Version table:
*** 5.2.1~cvs200911
500 http://
100 /var/lib/
Changed in pyqwt5 (Ubuntu): | |
assignee: | nobody → Scott Kitterman (kitterman) |
Changed in pyqwt5 (Ubuntu Trusty): | |
assignee: | Scott Kitterman (kitterman) → nobody |
Additional infos:
I just tried the qwt5 examples with c++: They work. So the segfault must have to do with the Python bindings.
The two changes in saucy according to the changelog are:
* No change rebuild to get a higher version than the sip4 breaks
* No-change rebuild for sip-api dependency
The qpycore_ get_lazy_ attr() function that causes the segfault is called from within sip. So the problem might have to do with a failed rebuild a changed API of sip or similar.