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

[Nick Roberts]

 > There is a project called "pydb" which seems to improve upon PDB:
 > 
 > http://bashdb.sourceforge.net/pydb/
 > 
 > They claim to have "gdb-style signal handling".
 > It comes with an Emacs mode:

The debugger (gud-pdb-command-name) was set the this at one time but Dave Love
got me to revert it back to pdb.

 > http://wiki.showmedo.com/index.php/PythonBernsteinPydbIntro
 > 
 > Unfortunately, comint-stop-subjob doesn't do much - pydb just prints  
 > "program received SIGINT", but doesn't interrupt the program.
 > 
 > It seems like it is set up to handle the signal:
 > 
 > (Pydb) handle SIGINT
 > Signal        Stop   Print   Stack   Pass    Description
 > SIGINT        Yes    Yes     No      No      Interrupt
 > 
 > ... but it doesn't do this. I don't understand why. I'm cc'ing the  
 > appropriate mailing list - maybe they can shed some light on this.

We need someone who uses Python to deal with this, but for some reason
(historical, perhaps) Python developers are more aligned with XEmacs. Pdbtrack
is meant to be better for debugging Python programs and, on more than one
occasion, I have posted a patch (python.el) here for this.  It's not been
committed because the some of the authorship is unclear.  However, you might
want to resurrect it for Aquamacs

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