Re: gnus still routinely crashes xemacs 2.4.8

A> #4 0x08095b05 in funcall_compiled_function () A> Cannot access memory at address 0x1 It looks like you're compiling without -g. We really need the line information that that gives us, or it's chasing needles in a haystack. It also is certain that your stack is corrupted. It would be very helpful if you could run XEmacs under the debugger, make it crash, then give us the backtrace from the debugger. Something like $ gdb /path/to/xemacs | tee debug.log (gdb) run -vanilla # make XEmacs crash here (gdb) bt (gdb) quit should work, leaving the backtrace in ./debug.log. We also would like to see the Installation file of the XEmacs that was crashing; you sent us one for 21.1.14, which is not causing you any problems, right? -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py