On Thu, 25 Aug 2011 17:18:13 +0200, Erik Janssens
wrote:
> Hi,
>
> After lots of tries I have been able to get a stacktrace
> + core of a segfault that I believe occurs from time to time.
>
> The attached stacktrace shows the segfault is inside the QT
> event loop, without even involving Python.
BTW: I often get a helpful stacktrace after a segfault with
faulthandler (http://pypi.python.org/pypi/faulthandler/). I only have
to enable it once in my project.
On Thu, Aug 25, 2011 at 3:18 PM, Erik Janssens
wrote:
> Hi,
>
> After lots of tries I have been able to get a stacktrace
> + core of
I've tried to create a test case for the previously reported
issue.
It appears the bug does not appear when the queued slot call
is made after the sender has been deleted, but only if the
call is made while the sender is deleted.
To run the case, use :
python -m nose.core \\
test_qt_bindings.py:
Hi,
After lots of tries I have been able to get a stacktrace
+ core of a segfault that I believe occurs from time to time.
The attached stacktrace shows the segfault is inside the QT
event loop, without even involving Python.
What I believe that happens is this :
1) A signal is connected to a s
