bug-report

Mario Natiello writes: This tells us very little; 0x8 is obviously outside of the XEmacs address space. We need a C backtrace which you can get EITHER by running XEmacs under gdb (eg, if XEmacs is installed you can use "gdb `which xemacs` | tee /tmp/gdb.log"), eliciting the crash, typing "bt" at the gdb prompt, and then mail us the file /tmp/gdb.log, OR by enabling core files with "ulimit -c unlimited" in your shell, then running XEmacs normally. When you get the crash, then find the core file (this is system- dependent, see your system's documentation), and assuming for example it's in "/path/to/core", type "gdb `which xemacs` /path/to/core | tee gdb.log" and continue as above. You may also have better luck with a more recent version of XEmacs; current one is 21.5.28 and several crashes were fixed since 21.5.27. This one doesn't ring a bell so I would like to see the C backtrace even if 21.5.28 works better for you. Thanks for your report, and thank you for using XEmacs! _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta