Attachment 4359 Details for Bug 11254 – output when xemacs is launched from a console

output when xemacs is launched from a console

emacs_bug (text/plain), 2.37 KB, created by Juergen Harms on 2013-09-18 12:20:07 CEST

(hide)

Description:

Filename:

MIME Type:

Creator: Juergen Harms

Created: 2013-09-18 12:20:07 CEST

Size: 2.37 KB

patch

obsolete

>Fatal error (11).
>
>Your files have been auto-saved.
>Use `M-x recover-session' to recover them.
>
>Your version of XEmacs was distributed with a PROBLEMS file that  may describe
>your crash, and with luck a workaround.  Please check it first, but do report
>the crash anyway.  Please report this bug by invoking M-x report-emacs-bug,
>or by selecting `Send Bug Report' from the Help menu.  If necessary, send
>ordinary email to `xemacs-beta@xemacs.org'.  *MAKE SURE* to include the XEmacs
>configuration from M-x describe-installation, or equivalently the file
>Installation in the top of the build tree.
>
>*Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely
>to be able to analyze the problem.  Locate the core file produced as a result
>of this crash (often called `core' or `core.<process-id>', and located in
>the directory in which you started XEmacs or your home directory), and type
>
>  gdb /usr/bin/xemacs core
>
>then type `where' at the debugger prompt.  No GDB on your system?  You may
>have DBX, or XDB, or SDB.  (Ask your system administrator if you need help.)
>If no core file was produced, enable them (often with `ulimit -c unlimited'
>in case of future recurrance of the crash.
>
>Lisp backtrace follows:
>
>  dispatch-non-command-events()
>  # (condition-case ... . ((nil)))
>  progress-feedback-dispatch-non-command-events()
>  # bind (tmsg top frame value message label)
>  append-progress-feedback(font-lock "Fontifying *scratch*..." 0 nil)
>  # bind (frame value message label)
>  display-progress-feedback(font-lock "Fontifying *scratch*..." 0)
>  # bind (str)
>  # (unwind-protect ...)
>  # bind (args value fmt label)
>  progress-feedback-with-label(font-lock "Fontifying %s..." 0 "*scratch*")
>  # bind (maybe-loudly end beg)
>  font-lock-default-unfontify-region(1 1 t)
>  # bind (loudly end beg)
>  font-lock-unfontify-region(1 1 t)
>  # bind (was-on font-lock-verbose font-lock-message-threshold aborted)
>  # (unwind-protect ...)
>  font-lock-default-fontify-buffer()
>  # bind (font-lock-verbose)
>  font-lock-fontify-buffer()
>  # bind (on-p maximum-size arg)
>  font-lock-mode()
>  (lambda nil (text-mode) (turn-on-auto-fill) (font-lock-mode))()
>  # (unwind-protect ...)
>  # bind (command-line-args-left)
>  command-line()
>  # (condition-case ... . ((t (byte-code "      ï¿½ï¿½" ... 1))))
>  # bind (error-data)
>  normal-top-level()
>  # (condition-case ... . error)
>  # (catch top-level ...)
>Segmentation fault

Fatal error (11).

Your files have been auto-saved.
Use `M-x recover-session' to recover them.

Your version of XEmacs was distributed with a PROBLEMS file that  may describe
your crash, and with luck a workaround.  Please check it first, but do report
the crash anyway.  Please report this bug by invoking M-x report-emacs-bug,
or by selecting `Send Bug Report' from the Help menu.  If necessary, send
ordinary email to `xemacs-beta@xemacs.org'.  *MAKE SURE* to include the XEmacs
configuration from M-x describe-installation, or equivalently the file
Installation in the top of the build tree.

*Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely
to be able to analyze the problem.  Locate the core file produced as a result
of this crash (often called `core' or `core.<process-id>', and located in
the directory in which you started XEmacs or your home directory), and type

  gdb /usr/bin/xemacs core

then type `where' at the debugger prompt.  No GDB on your system?  You may
have DBX, or XDB, or SDB.  (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited'
in case of future recurrance of the crash.

Lisp backtrace follows:

  dispatch-non-command-events()
  # (condition-case ... . ((nil)))
  progress-feedback-dispatch-non-command-events()
  # bind (tmsg top frame value message label)
  append-progress-feedback(font-lock "Fontifying *scratch*..." 0 nil)
  # bind (frame value message label)
  display-progress-feedback(font-lock "Fontifying *scratch*..." 0)
  # bind (str)
  # (unwind-protect ...)
  # bind (args value fmt label)
  progress-feedback-with-label(font-lock "Fontifying %s..." 0 "*scratch*")
  # bind (maybe-loudly end beg)
  font-lock-default-unfontify-region(1 1 t)
  # bind (loudly end beg)
  font-lock-unfontify-region(1 1 t)
  # bind (was-on font-lock-verbose font-lock-message-threshold aborted)
  # (unwind-protect ...)
  font-lock-default-fontify-buffer()
  # bind (font-lock-verbose)
  font-lock-fontify-buffer()
  # bind (on-p maximum-size arg)
  font-lock-mode()
  (lambda nil (text-mode) (turn-on-auto-fill) (font-lock-mode))()
  # (unwind-protect ...)
  # bind (command-line-args-left)
  command-line()
  # (condition-case ... . ((t (byte-code "      ï¿½ï¿½" ... 1))))
  # bind (error-data)
  normal-top-level()
  # (condition-case ... . error)
  # (catch top-level ...)
Segmentation fault

Actions: View

Attachments on bug 11254: 4359 | 4362 | 4503 | 7118