Re: xemacs crash due to no X server

Jan> Even though xemacs could never start in this situation, I Jan> would not expect it to coredump or crash in this manner. I'll take a look, but I think the problem is that X doesn't give you much of a way to determine that the IO error is due to absence of a server. Note that we're well into X, and a generic IO error handler is being called. At that point, we probably don't have enough context to know that there never was an X display. The philosophy is to just crash if we don't know what's going on. The standard graceful exit does things like save files and so on, and that could be very bad if XEmacs's internal state is wrong. Jan> #30 0x080add68 in xemacs_21_4_6_i386_redhat_linux () You might also try a more recent XEmacs version, as a bug where XEmacs got very confused by the absence of an XE server got fixed around 21.4.11. I don't think that will help, but you never know.... -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.