After running for four days, Python program stalled

[Chris Mellon]

On Dec 12, 2007 1:34 PM, John Nagle <nagle at animats.com> 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
>
> 77FA1428   mov         ecx,dword ptr [ebp-10h]
> 77FA142B   mov         dword ptr fs:[0],ecx
> 77FA1432   pop         edi
> 77FA1433   pop         esi
> 77FA1434   pop         ebx
> 77FA1435   leave
> 77FA1436   ret         10h
> 77FA1439   cmp         dword ptr [ebp-24h],0
> 77FA143D   je          77FA1447
> 77FA143F   push        dword ptr [ebp-24h]
> 77FA1442   call        77F8B5DF
> 77FA1447   ret
> 77FA1448   ret         4
> 77FA144B   int         3                                # STALLED HERE
> 77FA144C   ret
> 77FA144D   int         3
> 77FA144E   ret
> 77FA144F   mov         eax,dword ptr [esp+4]
> 77FA1453   int         3
> 77FA1454   ret         4
> 77FA1457   mov         eax,dword ptr [ebp-14h]
> 77FA145A   mov         eax,dword ptr [eax]
> 77FA145C   mov         eax,dword ptr [eax]
> --


Use a tool like sysinternal procexp to get more useful information
about the programs state, like what threads there are and a stack
trace with symbols of the each thread.