After running for four days, Python program stalled
Neil Hodgson
nyamatongwe+thunder at gmail.com
Wed Dec 12 16:26:39 EST 2007
More information about the Python-list mailing list
Wed Dec 12 16:26:39 EST 2007
- Previous message (by thread): Is anyone happy with csv module?
- Next message (by thread): After running for four days, Python program stalled
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message (by thread): Is anyone happy with csv module?
- Next message (by thread): After running for four days, Python program stalled
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list