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

List:       pykde
Subject:    Re: [PyKDE] strange seg fault with SIGNAL('PyObject *')
From:       Phil Thompson <phil () riverbankcomputing ! co ! uk>
Date:       2006-03-23 9:37:29
Message-ID: 200603230937.29124.phil () riverbankcomputing ! co ! uk
[Download RAW message or body]

On Thursday 23 March 2006 3:47 am, Patrick Stinson wrote:
> I don't have debuggin symbols installed, but I am consistently getting a
> seg fault after calling the python slot connected to SIGNAL('PyObject *')
> from a QWidget subclass. I am usually passing a python string with the
> signal, but if I pass None instead, it doesn't crash. I have a button group
> emitting clicked(QAbstractButton *), which emits this signal.
>
> the connecting code is as follows (sorry for the length), good luck:

I need a test case that I can actually run. This depends on additional local 
data. Also you have 3 different pieces of code commented out - which (all?) 
need to be changed to trigger the problem?

Phil

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]