Re: python(pdb) & gud: "stop" causes uncaught exception

[Nick Roberts]

 > Pressing the "stop" button in gud with pdb running (gud-stop-subjob)  
 > causes an unhandled python exception (stack trace below).

Yes, I've seen this too.  I couold make the "stop" button invisible for pdb but
the underlying is with comint-stop-subjob which is on the menubar of the GUD
buffer and C-c C-z.

 >...
 > KeyboardInterrupt
 > Uncaught exception. Entering post mortem debugging
 > Running 'cont' or 'step' will restart the program
 >  > /usr/local/lib/python2.4/cmd.py(151)cmdloop()
 > -> pass
 > (Pdb)

All comint-stop-subjob does is send SIGINT to the process.  When a program runs
under GDB, SIGINT is intercepted by GDB and not normally passed on to the
program, but pdb doesn't seem to do this. If you run a pythons script under pdb
from the command line and type ^C then you should get the same result that you
see in Emacs.

So the question is:  How do you interrupt a python script that is being
debugged?


-- 
Nick                                           http://www.inet.net.nz/~nickrob