Message148439
I confirm the bug. But I don't think disabling Ctrl-C (SIGINT) handling by default is a good idea. Proper Ctrl-C support seems like a fundamental feature for a command line debugger.
However, I think the bug is easily fixable w/o changing SIGINT handling. Basically, just put try/except around signal.signal, catch the ValueError and proceed. Would this approach solve your problem?
Patch attached.
PS. and here is a small program demonstrating the bug (just run it and execute "c" command at pdb prompt)
import threading
import pdb
def start_pdb():
pdb.Pdb().set_trace()
x = 1
y = 1
t = threading.Thread( target=start_pdb)
t.start() |
|
Date |
User |
Action |
Args |
2011-11-27 03:10:58 | isandler | set | recipients:
+ isandler, bpb |
2011-11-27 03:10:58 | isandler | set | messageid: <1322363458.63.0.77529451573.issue13120@psf.upfronthosting.co.za> |
2011-11-27 03:10:58 | isandler | link | issue13120 messages |
2011-11-27 03:10:57 | isandler | create | |
|