>>>> "paul" == paul beckett <(JIC)"
<paul.beckett(a)bbsrc.ac.uk>> writes:
Nothing very helpful. We absolutely need to know where in the code
XEmacs crashed and what version and platform it is. XEmacs sources
are about 30MB now and _none_ of it causes crashes that we know about.
Please try _really_ hard to get us the backtrace from the core dump
(many shells will allow the dump with a command like "ulimit -c
unlimited", that's bash-specific). Or even better you can run under
the debugger. My favorite is
gdb `which xemacs` | tee gdb.out
(gdb) run web_query.pl
(gdb) where
(gdb) quit
Something similar should be possible with dbx.
If you can get XEmacs running at all, M-x report-xemacs-bug RET will
help a lot, giving almost all the information we need automatically,
although you have to collect the stack trace yourself.
--
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.