On Mon, Aug 2, 2010 at 10:10 AM, Ilya Sandler <ilya.sand...@gmail.com> wrote: > Hello, > > I'm the submitter of the original patch and would like to help with it if I > can. > >> One issue that's not yet closed is #7245, which adds a (very nice IMO) >> feature: when you press Ctrl-C while the program being debugged runs, >> you will not get a traceback but execution is suspended, and you can >> debug from the current point of execution -- just like in gdb. >> >> However, there were apparently issues with some of the buildbots when >> the patch was applied for a short time. I also don't know how and if >> it works on Windows, so I'd need some helpful people testing it. > > For whatever it's worth, it worked for me with python trunk (2.x) on > Vista, when I tried it manually. But I don't know how to implement > the unit test there (subprocess module doesn't support sending SIGINT > programmatically on windows either). So the test_pdb2 test does not > check signal behavior on Windows platforms.
I haven't looked at the relevant patch to check if this is applicable to the test case, but actually sending a Ctrl-C character to stdin (via a pipe) can work (although I think there can be some weirdness if the parent process has no console). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com