Kenneth Loafman writes: First, please reproduce the problem, then immediately use M-x report-xemacs-bug to report the bug. It provides a traceback of any keys you pressed, plus a lot of general information about your installation that may or may not be useful. (Most importantly, on Debian-derived installations it's very likely that you have multiple versions of Lisp libraries installed; M-x report-xemacs-bug will tell us which ones XEmacs can *find*, and then which one it will actually *load*.) Don't forget to check the keystroke traceback for passwords and other sensitive data. Keystroke counts can sometimes be important; please obscure rather than delete such data. We can hope that the keystroke sequence will provide a reproduction recipe. In the report, answer the following questions (without going to inordinate amounts of effort, of course; if you already have multiple versions of Python and their corresponding pdbs installed, please do try them, but whether you should upgrade Python or something like that depends on how much effort that would be for you) and anything similar that you can think of: 1. pdb.el depends on an external program, pdb. Where can we get it? (In the following, pdb.el refers to pdb.el in XEmacs, and pdb refers to the external program plus any support like Python.) What version of pdb doesn't work? Are there any that do? Is it possible that you have multiple versions of Python and pdb and there's a version mismatch there? 2. Does pdb work from the command line? Does it work from an M-x shell buffer in XEmacs? 3. Did pdb.el ever work? If so, what versions of pdb.el, the XEmacs package containing it, and XEmacs worked? 4. What version(s) of Python don't work? Do you know any that do? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta