xemacs 21.5 b28 segfaults upon exit on aix 5.2

Thomas Mittelstaedt writes: Can you just run XEmacs under gdb all the time? (For me this doesn't seem to cost anything but about 1MB of virtual memory.) It is often the case that the debugger is somehow able to save the backtrace, although it can't get a good one from the core file. The one above says that fatal_error_signal was called literally from nowhere, which isn't very helpful. This says that some Lisp object was of unexpected type, but it doesn't help us figure out how it got there. All I can advise is caution. The Lisp backtrace says Dired was doing something, but that's not very helpful either (Lisp errors cannot crash XEmacs, it has to be a problem in the C code). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta