Peter Seibel <[EMAIL PROTECTED]> writes: > Okay, here's another strange one which has happened a few times. I'll > get an error in the minibuffer that says: > > Symbol's value as variable is void: nil > > No matter what I do I continue to get that error or something similar > such as: > > Error in pre-command-hook: (void-variable nil) > > I can type 'q' to the ediff window and it'll ask if I want to quit but > when I type 'y' it goes back to: > > Symbol's value as variable is void: nil > > I realize that this is probably just more symptoms of memory > corruption but maybe one of these details will give someone an aha > moment.
We have had occasional reports of crashes related to the cons list before, but I really wonder why you see them so consistently. E.g. I use ediff too and haven't seen any problems... What kind of files do you compare with ediff? Any special character set or encoding in those files? What does M-x list-processes show ? > (BTW, is there a way to interrupt emacs without killing it so > I can get a backtrace from GDB?) C-z in gdb. -- Kim F. Storm <[EMAIL PROTECTED]> http://www.cua.dk _______________________________________________ Emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
