Re: segm fault: file in another folder

Bart> But all the other editors simply open and give one a chance Bart> to find the missing file by going to the correct folder. Why Bart> do you crash? If we knew why, it wouldn't. I've never seen XEmacs crash that way, nor heard of it before. I rather suspect its something else in the initialization. Unfortunately, your report is useless for fixing it; the source code for XEmacs is about 30MB now, and we do not know of any of it that causes a crash. We need a file and a line number where the crash occurred, which the core dump should provide. I infer that you are able to reproduce the crash. Good. This time, start XEmacs with the commands bash$ gdb `which xemacs` # note backquotes (gdb) run essay11.tex Then when XEmacs crashes, (gdb) where and collect the output and send it to us. Alternatively start by doing `ulimit -c unlimited' in the xterm, then start xemacs in exactly the same way. When xemacs crashes, there should be a core file in the current directory, named core. Do `gdb `which xemacs` core', then type `where' at the gdb prompt and collect the output and send it to us. However, running under gdb is preferred because gdb is likely to preserve the stack better. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Don't ask how you can "do" free software business; ask what your business can "do for" free software.