Re: Xemacs 21.5.b14

Ivan> But the most common (detectable) problem occurs by using any Ivan> option related to "FIND", as soon as you click that option, Ivan> the application crashes, generating a core file with the Ivan> following information. Hopefully you will know what is all Ivan> about. You probably have a Motif build. If you want a semi-stable build in the 21.5 series, avoid use of Motif. (Yes, Motif is standard. The problem is that nothing in X ever sanity-checks arguments, and Motif is even less robust than the rest of X to bad arguments. Very hard to debug.) Ivan> #6 0xe521c in Feval () You have a stripped binary. If you build your own, don't do that; we need to see the arguments being passed to the functions to understand the behavior, especially where things went wrong. Ivan> #10 0x3158c8 in vars_of_frame_x () Ivan> #11 0x1c61a0 in redisplay_widget () Your stack is most likely corrupt. The vars_of_* functions should only ever be called at startup time; redisplay_widget() definitely doesn't call any vars_of_* function. If possible, run XEmacs under the debugger which may be able to preserve the stack. -- 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.