[PyKDE] Debugging a segfault in Linux

[Mike Tammerman]

I checked all the __init__ functions, but I hadn't missed anything as
you mentioned. However, I catched another traceback which is smaller
and complete.

I searched the previous mails in the archieve and found these

http://mats.imk.fraunhofer.de/pipermail/pykde/2003-November/006529.html
http://mats.imk.fraunhofer.de/pipermail/pykde/2003-November/006508.html

They had also faced the same problem like mine, but there seems to be
no solution.

Mike

#0  0xb767e318 in QObject::parent (this=0x139) at qobject.h:154
#1  0xb767ebd5 in QWidget::parentWidget (this=0x139, sameWindow=false)
at qwidget.h:856
#2  0xb778fbb5 in ~QWidget (this=0x85fd868) at kernel/qwidget.cpp:946
#3  0xb6de0c48 in sipQWidget::~sipQWidget () from
/usr/lib/python2.4/site-packages/qt.so
#4  0xb7753b8e in QObject::event (this=0x85fd868, e=0x85f9f78) at
kernel/qobject.cpp:750
#5  0xb7791268 in QWidget::event (this=0x85fd868, e=0x85f9f78) at
kernel/qwidget.cpp:4658
#6  0xb6de3ec9 in sipQWidget::event () from
/usr/lib/python2.4/site-packages/qt.so
#7  0xb76edf80 in QApplication::internalNotify (this=0x82b6ba8,
receiver=0x85fd868, e=0x85f9f78)
    at kernel/qapplication.cpp:2635
#8  0xb76eecf6 in QApplication::notify (this=0x82b6ba8,
receiver=0x85fd868, e=0x85f9f78)
    at kernel/qapplication.cpp:2523
#9  0xb6dff877 in sipQApplication::notify () from
/usr/lib/python2.4/site-packages/qt.so
#10 0xb767edb7 in QApplication::sendEvent (receiver=0x85fd868,
event=0x85f9f78) at qapplication.h:491
#11 0xb76ef4a3 in QApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qapplication.cpp:3261
#12 0xb76ef5aa in QApplication::sendPostedEvents () at
kernel/qapplication.cpp:3172
#13 0xb769206c in QEventLoop::processEvents (this=0x83bd4c0, flags=4)
at kernel/qeventloop_x11.cpp:202
#14 0xb7705cfb in QEventLoop::enterLoop (this=0x83bd4c0) at
kernel/qeventloop.cpp:198
#15 0xb76ecc3f in QApplication::enter_loop (this=0x82b6ba8) at
kernel/qapplication.cpp:2790
#16 0xb6e026b3 in sipQApplication::sipEmit_guiThreadAwake () from
/usr/lib/python2.4/site-packages/qt.so
#17 0x080b6a11 in PyEval_EvalFrame ()
#18 0x080b726d in PyEval_EvalCodeEx ()
#19 0x080b5719 in PyEval_EvalFrame ()
#20 0x080b726d in PyEval_EvalCodeEx ()
#21 0x080b73ae in PyEval_EvalCode ()
#22 0x080d8ffc in PyRun_FileExFlags ()
#23 0x080d929c in PyRun_SimpleFileExFlags ()
#24 0x08055a06 in Py_Main ()
#25 0xb7e5fea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#26 0x08054f21 in _start ()


On 3/17/06, Andreas Pakulat <apaku at gmx.de> wrote:
> On 17.03.06 17:14:54, Diez B. Roggisch wrote:

> This often happens when deriving from a Qt class and not doing
>
> Q<Blah>.__init__(self)
>
> within the new class' __init__ method. However IIRC Python or sip tells
> you then that the underlying C++ Object "vanished".
>
> Andreas
>
> --
> You'll never see all the places, or read all the books, but fortunately,
> they're not all recommended.
>
> _______________________________________________
> PyKDE mailing list    PyKDE at mats.imk.fraunhofer.de
> http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
>