Xavier de Gaye added the comment: The run, runeval and runcall methods run the debugging session in a try/finally clause and set the global trace function to None in the finally clause. But set_trace does not run in a try/finally, hence the problem. A possible fix is to ensure that the bottom frame has a local trace function and to set the global trace function to None when returning from that frame. See how this is fixed at http://code.google.com/p/pdb-clone/source/detail?r=ee22a278c743ea9449a3e7618acc7c33cb11bb26&name=2.7
---------- nosy: +xdegaye _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13044> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
