JAT> why couldn't I get a lisp backtrace? had debug-on-error set to JAT> t, but all I could get was the backtrace in gdb... GN> I might be wrong but... GN> GN> The lisp backtrace comes out on stdout/stderr of whereever you GN> started XEmacs from (along with a whole lot of other output about GN> your files being saved and to whom to complain). Since I started GN> XEmacs from a terminal window (which I leave around for these GN> occassions) I had that info handy. yes, I leave the terminal around as well, and I don't background gdb, but still don't get a lisp backtrace... maybe it's because I'm using Cygnus' gdb with the Insight frontend? maybe I'll try starting gdb w/o the GUI and see if that helps... GN> If you start your XEmacs from GN> a menu supplied by your windowing system, then the stdout goes GN> either into the bit bucket or to a file specifically designated to GN> log this kind of output (depends on your window system). I don't do that... I just do gdb `which xemacs` in a term window... -JT