On Saturday 22 April 2006 11:19 pm, Simon Edwards wrote:
On Saturday 22 April 2006 21:17, Phil Thompson wrote:
On Saturday 22 April 2006 4:04 pm, Simon Edwards wrote:
I'm confused as to what the newer exec_loop() code in QDialog was meant
to do.
-
%If
Hello,
I've spent some more time playing with this problem some more. (See
attachment). I've added some dumpObjectTree() calls and debug for the __del__
methods for the two dialogs. To me it clears looks like SIP and Python
disagree about who is responsible for destroying the popup dialog.
On Saturday 22 April 2006 4:04 pm, Simon Edwards wrote:
Hello,
I've spent some more time playing with this problem some more. (See
attachment). I've added some dumpObjectTree() calls and debug for the
__del__ methods for the two dialogs. To me it clears looks like SIP and
Python disagree
On Saturday 22 April 2006 21:17, Phil Thompson wrote:
On Saturday 22 April 2006 4:04 pm, Simon Edwards wrote:
I'm confused as to what the newer exec_loop() code in QDialog was meant to
do.
-
%If (Qt_3_0_0 -)
int exec() /PyName=exec_loop, ReleaseGIL,
On Saturday 11 March 2006 20:26, Phil Thompson wrote:
On Saturday 11 March 2006 7:13 pm, Simon Edwards wrote:
Anyway, I think I've come across a double free memory bug in PyQt 3.15.1.
Qt complains about a Double QObject deletion detected., and valgrind
points to a problem in
On Sunday 12 March 2006 10:04 am, Simon Edwards wrote:
On Saturday 11 March 2006 20:26, Phil Thompson wrote:
On Saturday 11 March 2006 7:13 pm, Simon Edwards wrote:
Anyway, I think I've come across a double free memory bug in PyQt
3.15.1. Qt complains about a Double QObject deletion
On Sunday 12 March 2006 07:04, Phil Thompson wrote:
On Sunday 12 March 2006 10:04 am, Simon Edwards wrote:
On Saturday 11 March 2006 20:26, Phil Thompson wrote:
On Saturday 11 March 2006 7:13 pm, Simon Edwards wrote:
Anyway, I think I've come across a double free memory bug in PyQt
Hi Phil and everybody else,
I'm busy working on polishing and debugging stuff for the coming Kubuntu
release, which makes increasingly more use of PyQt+PyKDE BTW.
Anyway, I think I've come across a double free memory bug in PyQt 3.15.1. Qt
complains about a Double QObject deletion detected.,
On Saturday 11 March 2006 7:13 pm, Simon Edwards wrote:
Hi Phil and everybody else,
I'm busy working on polishing and debugging stuff for the coming Kubuntu
release, which makes increasingly more use of PyQt+PyKDE BTW.
Anyway, I think I've come across a double free memory bug in PyQt 3.15.1.
Simon Edwards [EMAIL PROTECTED] wrote:
Anyway, I think I've come across a double free memory bug in PyQt 3.15.1.
Qt
complains about a Double QObject deletion detected., and valgrind points
to a problem in sipKDialogBase::~sipKDialogBase(). (Reading memory which
is
already free'd, and invalid
On Saturday 11 March 2006 11:13, Simon Edwards wrote:
Hi Phil and everybody else,
I'm busy working on polishing and debugging stuff for the coming Kubuntu
release, which makes increasingly more use of PyQt+PyKDE BTW.
Anyway, I think I've come across a double free memory bug in PyQt 3.15.1.
11 matches
Mail list logo