On 7/20/2007 11:22 AM, Phil Thompson wrote:
Can you detect the infinite loop and generate a backtrace?
Sure, but I doubt it'll be before next Monday.
I've nulled the pointers for tonight's snapshot, and made one other related
change (which hopefully won't introduce a new problem).
Thanks.
On Thursday 19 July 2007 7:56 pm, Giovanni Bajo wrote:
> On 18/07/2007 22.43, Phil Thompson wrote:
> > I copied the list removal code back into the destructor (keeping a
> > duped copy in the disable() slot), and it seems to work.
> >
> > Do you agree on this fix? Testcases are real
On 18/07/2007 22.43, Phil Thompson wrote:
I copied the list removal code back into the destructor (keeping a
duped copy in the disable() slot), and it seems to work.
Do you agree on this fix? Testcases are really hard and tiresome to
extract so I'd rather avoid it if it's not really really nece
On Wednesday 18 July 2007 6:28 pm, Giovanni Bajo wrote:
> On 7/18/2007 10:32 AM, Giovanni Bajo wrote:
> >>> I copied the list removal code back into the destructor (keeping a
> >>> duped copy in the disable() slot), and it seems to work.
> >>>
> >>> Do you agree on this fix? Testcases are really ha
On 7/18/2007 10:32 AM, Giovanni Bajo wrote:
I copied the list removal code back into the destructor (keeping a duped
copy in the disable() slot), and it seems to work.
Do you agree on this fix? Testcases are really hard and tiresome to
extract so I'd rather avoid it if it's not really really ne
On 7/17/2007 3:47 PM, Phil Thompson wrote:
I copied the list removal code back into the destructor (keeping a duped
copy in the disable() slot), and it seems to work.
Do you agree on this fix? Testcases are really hard and tiresome to
extract so I'd rather avoid it if it's not really really nec
On Tuesday 17 July 2007 2:34 pm, Giovanni Bajo wrote:
> On 7/16/2007 2:36 PM, Phil Thompson wrote:
> > This will be fixed in tonight's PyQt snapshot.
> >
> > The proxy created to handle the signal was being incorrectly reused by a
> > new QObject created at the same address as the one the proxy was
On 7/16/2007 2:36 PM, Phil Thompson wrote:
This will be fixed in tonight's PyQt snapshot.
The proxy created to handle the signal was being incorrectly reused by a new
QObject created at the same address as the one the proxy was created for.
Because there is no event processing going on, the p
On 7/16/2007 2:36 PM, Phil Thompson wrote:
On Tuesday 10 July 2007 5:42 pm, Giovanni Bajo wrote:
Hi Phil,
a little crasher:
==
from PyQt4.QtCore import *
app = QCoreApplication([])
for i in range(300):
print i
w1 = QObject(None)
w2 =
On Tuesday 10 July 2007 5:42 pm, Giovanni Bajo wrote:
> Hi Phil,
>
> a little crasher:
>
> ==
> from PyQt4.QtCore import *
>
> app = QCoreApplication([])
> for i in range(300):
> print i
> w1 = QObject(None)
> w2 = QObject(None)
> prin
On Wednesday 11 July 2007 11:51 am, Giovanni Bajo wrote:
> On Wed, 11 Jul 2007 12:05:29 +0200, Ulrich Berning
>
> <[EMAIL PROTECTED]> wrote:
> > It crashes on all my platforms (all 32 bit):
> > AIX 4.3
> > HP-UX 11.00
> > IRIX 6.5
> > Solaris 8
> > SuSE Linux 9.2
> > Windows 2000
> >
> >
> > I'm us
On Wed, 11 Jul 2007 12:05:29 +0200, Ulrich Berning
<[EMAIL PROTECTED]> wrote:
> It crashes on all my platforms (all 32 bit):
> AIX 4.3
> HP-UX 11.00
> IRIX 6.5
> Solaris 8
> SuSE Linux 9.2
> Windows 2000
>
>
> I'm using:
> Python-2.5.1
> Qt-4.3.0
> sip-snapshot-20070704
> PyQt4-snapshot-2007070
Phil Thompson wrote:
Hmm, works for me (even if I up the loop count to 3000).
Can anybody else reproduce it? Are you on a 32 or 64 bit system?
It crashes on all my platforms (all 32 bit):
AIX 4.3
HP-UX 11.00
IRIX 6.5
Solaris 8
SuSE Linux 9.2
Windows 2000
I'm using:
Python-2.5.1
Qt-4.3.0
On Wednesday 11 July 2007 7:46 am, Giovanni Bajo wrote:
> On 11/07/2007 3.24, Tuvi, Selim wrote:
> > My run did not crash but it mysteriously exit after three iterations:
> >
> > C:\projects\LICOS\temp\qt4>python crash.py
> > 0
> > 12133768 12133840
> > 1
> > 12133912 12133768
> > 2
> > 12133840 12
On 11/07/2007 3.24, Tuvi, Selim wrote:
My run did not crash but it mysteriously exit after three iterations:
C:\projects\LICOS\temp\qt4>python crash.py
0
12133768 12133840
1
12133912 12133768
2
12133840 12133912
C:\projects\LICOS\temp\qt4>
I can run it multiple times with the same result.
P
mputing.com
> Subject: Re: [PyQt] Re: Crash with shortcircuit signals
>
> On Wednesday 11 July 2007 00:00:38 Phil Thompson wrote:
> [...]
> > Hmm, works for me (even if I up the loop count to 3000).
> >
> > Can anybody else reproduce it? Are you on a 32 or 64 bit syst
On 10/07/2007 23.00, Phil Thompson wrote:
On Tuesday 10 July 2007 5:42 pm, you wrote:
Hi Phil,
a little crasher:
==
from PyQt4.QtCore import *
app = QCoreApplication([])
for i in range(300):
print i
w1 = QObject(None)
w2 = QObject(Non
On Wednesday 11 July 2007 00:00:38 Phil Thompson wrote:
[...]
> Hmm, works for me (even if I up the loop count to 3000).
>
> Can anybody else reproduce it? Are you on a 32 or 64 bit system?
Can reproduce here on 32bit , sip 20070625, PyQt4 20070625, Qt 4.3.0
[~]> python test.py
0
-1480848532 -148
On Tuesday 10 July 2007 5:42 pm, you wrote:
> Hi Phil,
>
> a little crasher:
>
> ==
> from PyQt4.QtCore import *
>
> app = QCoreApplication([])
> for i in range(300):
> print i
> w1 = QObject(None)
> w2 = QObject(None)
> print id(w1),
19 matches
Mail list logo
