Bug in the python bindings? [was: Plasma crashing with QGraphicsLinearLayout.addStretch]
wolter at informatik.uni-bremen.de
Thu May 7 18:36:48 CEST 2009
Aaron J. Seigo wrote:
> On Wednesday 06 May 2009, Johannes Wolter wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0xb3db9720 (LWP 11622)]
> > 0xb741e737 in QGraphicsLayoutItem::isLayout () from
> > /usr/lib/libQtGui.so.4 (gdb) bt
> > #0 0xb741e737 in QGraphicsLayoutItem::isLayout () from
> > /usr/lib/libQtGui.so.4 #1 0xa85debf1 in ?? () from
> > /usr/lib/pymodules/python2.5/PyQt4/QtGui.so #2 0xa8b60bdd in
> > PyCFunction_Call (func=0xa7078a6c, arg=0xa772a48c, kw=0x0) at
> > ../Objects/methodobject.c:73 #3 0xa8bb2f09 in PyEval_EvalFrameEx
> > (f=0x846620c, throwflag=0) at ../Python/ceval.c:3612 #4 0xa8bb3e3f in
> looks like a bug in the python bindings, perhaps?
Can anyone give me a hint how to debug this problem? From the backtrace it
looks like the bindings are generated via SIP, which I'm not familiar with.
> (others on the list: note that Johannes is not sub'd to the list and so
> would probably appreciate being kept in the CC's)
Now I am.
Thanks for any suggestion,
Cognitive Neuroinformatics, University of Bremen
Office: Cartesium 04.051 Phone: +49(0)421-218-64218
More information about the Plasma-devel