Re: After running for four days, Python program stalled

2007-12-12 Thread Neil Hodgson
John Nagle: > Had a Python program stall, using no time, after running OK for four days. > Python 2.4, Windows. Here's the location in Python where it's stalled. > Any idea what it's waiting for? > 77FA144B int 3# STALLED HERE Its a breakpoint instru

Re: After running for four days, Python program stalled

2007-12-12 Thread James Matthews
INT 3 is a debug interrupt:-) On Dec 12, 2007 8:41 PM, Chris Mellon <[EMAIL PROTECTED]> wrote: > On Dec 12, 2007 1:34 PM, John Nagle <[EMAIL PROTECTED]> wrote: > > Had a Python program stall, using no time, after running OK for four > days. > > Python 2.4, Windows. Here's the location in Python

Re: After running for four days, Python program stalled

2007-12-12 Thread Chris Mellon
On Dec 12, 2007 1:34 PM, John Nagle <[EMAIL PROTECTED]> wrote: > Had a Python program stall, using no time, after running OK for four days. > Python 2.4, Windows. Here's the location in Python where it's stalled. > Any idea what it's waiting for? > > John Nagle > >

After running for four days, Python program stalled

2007-12-12 Thread John Nagle
Had a Python program stall, using no time, after running OK for four days. Python 2.4, Windows. Here's the location in Python where it's stalled. Any idea what it's waiting for? John Nagle 77FA1428 mov ecx,dword ptr [ebp-10h] 77FA142B mov dword