[PyKDE] Debugging a segfault in Linux

Mike Tammerman mtammerman at gmail.com
Fri Mar 17 16:29:44 GMT 2006

This question may be very silly, but is there a way to associate the
backtrace with my python script. Here is the backtrace of the core
file, that may be useful.

#0  0xb7656318 in QObject::parent (this=0xffffffff) at qobject.h:154
#1  0xb7656bd5 in QWidget::parentWidget (this=0xffffffff,
sameWindow=false) at qwidget.h:856
#2  0xb7767bb5 in ~QWidget (this=0x85e3ce0) at kernel/qwidget.cpp:946
#3  0xb77ed2ef in ~QFrame (this=0x85e3ce0) at qframe.h:48
#4  0xb780b5d5 in ~QLineEdit (this=0x85e3ce0) at widgets/qlineedit.cpp:442
#5  0xb77d5110 in QComboBox::setLineEdit (this=0x85ff618,
edit=0x8609050) at widgets/qcombobox.cpp:2258
#6  0xb6d88802 in sipQComboBox::sipEmit_textChanged () from
#7  0x080b6a11 in PyEval_EvalFrame ()


On 3/17/06, Diez B. Roggisch <deets at web.de> wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread -1209734944 (LWP 16726)]
> > 0xb7682318 in QObject::parent (this=0xffffffff) at qobject.h:154
> This looks fishy - a "this" with value -1 ist most probably an uninitialized
> pointer. Try investigating that.
> Diez
> _______________________________________________
> PyKDE mailing list    PyKDE at mats.imk.fraunhofer.de
> http://mats.imk.fraunhofer.de/mailman/listinfo/pykde

More information about the PyQt mailing list