After running for four days, Python program stalled

Discussion in 'Python' started by John Nagle, Dec 12, 2007.

  1. John Nagle

    John Nagle Guest

    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]
     
    John Nagle, Dec 12, 2007
    #1
    1. Advertising

  2. John Nagle

    Chris Mellon Guest

    On Dec 12, 2007 1:34 PM, John Nagle <> 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.
     
    Chris Mellon, Dec 12, 2007
    #2
    1. Advertising

  3. John Nagle

    Neil Hodgson Guest

    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 instruction and its likely you are running under a
    debugger that is failing to respond. You don't often see a bare 'int 3'
    in real code unmassaged by a debugger unless the developer wants an
    explicit break to debugger.

    Neil
     
    Neil Hodgson, Dec 12, 2007
    #3
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. David Stockwell
    Replies:
    2
    Views:
    703
    Anna Martelli Ravenscroft
    Sep 20, 2004
  2. Gerrit
    Replies:
    0
    Views:
    386
    Gerrit
    Sep 20, 2004
  3. Steven D'Aprano

    Stalled ticket in Python bug tracker

    Steven D'Aprano, Jan 23, 2009, in forum: Python
    Replies:
    6
    Views:
    270
    Peter Otten
    Jan 24, 2009
  4. basi
    Replies:
    6
    Views:
    128
  5. Michel Demazure

    nothing new in ruby_core for four days ?

    Michel Demazure, Jun 17, 2010, in forum: Ruby
    Replies:
    14
    Views:
    155
    Andreas S.
    Jun 17, 2010
Loading...

Share This Page