Stephen J. Turnbull writes:
Giacomo Boffi writes:
> I have built XEmacs with g++, but nothing has changed, at least to
> my eyes
OK. I'll try to reproduce this weekend.
> and here, in attachment, the gdb backtrace
Unfortunately, the backtrace doesn't tell what I need to know, which
is which test is triggering this.
Could you try starting XEmacs, and run M-x test-emacs-test-file RET
tests/automated/mule-tests.el, and see if you can figure out which
test is failing?
i started src/xemacs
i load-library test-harness
i find-file tests/automated/mule-tests.el
in the buffer with mule-tests
i required bytecomp
i eval-last-sexp on (defun test-chars ...)
i eval-last-sexp on (test-chars )
____ ___ ___ ___ __ __ _ _
| __ ) / _ \ / _ \ / _ \| \/ | | | |
| _ \| | | | | | | | | | |\/| | | | |
| |_) | |_| | |_| | |_| | | | | |_|_|
|____/ \___/ \___/ \___/|_| |_| (_|_)
notice that
1. if i had requested, via options menu, a backtrace on error then
XEmacs dies a sudden death
2. if i hadn't requested a backtrace, i get in the minibuffer the
SERIUOS XEMACS BUG ... save your buffers ...
message and XEmacs is still alive
i wonder if, in the second case, i could do something to get info on
what happened
i have also a core dump obtained for case 1 (here in attachment), and
it seems that the fatal error happens in the backtrace production
g
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta