[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    [PyQt] Debugging a segfault on win32/msvc
From:       Giuseppe Corbelli <giuseppe.corbelli () copanitalia ! com>
Date:       2012-06-21 14:32:51
Message-ID: 4FE33093.6010601 () copanitalia ! com
[Download RAW message or body]

Hi all
I have a fairly complex application with pyqt 4.8.5/qt 4.7.4/sip 4.12.4.

Randomly I experience segfaults. They may happen once in a week or once a day
and of course they happen on client sites. Interestingly enough machines that
run the same routine with same OS and software do not have the same behaviour.
Machine 1 segfaults at random, Machine 2 never segfaults.

I have a fat minidump created with
MiniDumpWithIndirectlyReferencedMemory
MiniDumpWithProcessThreadData
MiniDumpWithPrivateReadWriteMemory

Using the msvc debugger the call stack stops when calling
bool QCoreApplication::notifyInternal(QObject *receiver, QEvent *event)

The QEvent is a non spontaneous QTimerEvent.
The receiver is a QObject for which the d_ptr is NULL.
The only place where I use QTimers is to blink/change labels on the screen,
but the labels are children of form(s) being shown, so no garbage collection
should be applicable.

Well, I'm not an expert in the QT internals and I know this isn't exactly the
right mailing list, but any suggestion would be appreciated :-)

-- 
            Giuseppe Corbelli
WASP Software Engineer, Copan Italia S.p.A
Phone: +390303666104  Fax: +390302659932
E-mail: giuseppe.corbelli@copanitalia.com
_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]