crash and where is core?
Hello,
Sorry to disturb you, but my XEmacs when it came up had some small failure
"Error in init file: Symbol's value as variable is void: cache-overlay. I
checked the init file and it was empty. I have some .emacs in /etc/skel. I
am first time user of emacs. So, I had the idea that XEmacs is easier. Maybe
you can help me, although you must probably ask me precise instructions what
to do. But please answer me.
I decided to de-install the packages from RH8.0 which were connected with
XEmacs:
ddskk-xemacs-11.6.0-8
flim-xemacs-1.14.3-7
mew-xemacs-2.2-5
mutt-1.4-4
w3m-el-xemacs-1.3.1-1
xemacs-21.4.8-16
xemacs-el-21.4.8-1.6
xemacs-info-21.4.8-1.6
I installed them again package by package. There were no complaints.
However, when I started XEmacs up again and touched the scratch-window or
tried to open a file, XEmacs crashed. Of course I tried to find the core. I
did updatedb, but could not find under the myriad of files "core".
So, here is what I got from the lisp-side:
============================================
Fatal error: assertion failed, file bytecode.c, line 1477, abort()
Fatal error (6).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting `Send Bug Report'
from the help menu.
As a last resort send ordinary email to `crashes(a)xemacs.org'.
*MAKE SURE* to include the information in the command
M-x describe-installation.
If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type
gdb /usr/bin/xemacs core
then type `where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB. A similar procedure should work for all of
these. Ask your system administrator if you need more help.)
Lisp backtrace follows:
mmm-mode-on-maybe()
funcall(mmm-mode-on-maybe)
# (condition-case ... . ((error)))
# bind (--dolist-temp--29302 func)
mmm-run-major-mode-hook()
# (unwind-protect ...)
# bind (--dolist-temp--29303 buffer)
mmm-check-changed-buffers()
# (condition-case ... . error)
# (condition-case ... . error)
# (unwind-protect ...)
read-minibuffer-internal("Migrate init file to ~/.xemacs/? (yes or no) ")
byte-code("..." [standard-output standard-input prompt recursion-depth
minibuffer-depth t read-minibuffer-internal] 2)
# (catch exit ...)
# bind (mouse-grabbed-buffer current-prefix-arg
minibuffer-history-variable minibuffer-history-position
minibuffer-scroll-window)
# (unwind-protect ...)
# bind (minibuffer-default _history_ oconfig mconfig frame buffer window
oframe owindow dir default abbrev-table history readp keymap
initial-contents prompt) read-from-minibuffer("Migrate init file to
~/.xemacs/? (yes or no) " nil #<keymap minibuffer-local-map size 14 0xd88>
nil t nil nil)
# bind (minibuffer-completion-table default-value history initial-contents
prompt)
read-string("Migrate init file to ~/.xemacs/? (yes or no) " nil t)
# bind (p ans)
# (unwind-protect ...)
# bind (prompt)
yes-or-no-p-minibuf("Migrate init file to ~/.xemacs/? ")
# bind (standard-output)
maybe-migrate-user-init-file()
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
[root＠dsl156 root]#
[1]+ Aborted xemacs
==========================================================
with friendly greetings,
Peter van Summeren
_________________________________________________________________
Join the worlds largest e-mail service with MSN Hotmail.
http://www.hotmail.com