This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

xemacs crashes with SIGSEGV after update


today I updated all packages of my 32-Bit Cygwin installation (installed
on top of Windows 7). After that xemacs crashed if I tried to open a
file. Therefore I reinstalled the older version xemacs-
Unfortunately the older version crashes as well. I can start xemacs
without command line arguments.

hermes x 3 xemacs &
[1] 4908
hermes x 4 

It crashes if I try to open a file with <Ctrl-x><Ctrl-f> or if I start
xemacs with a filename as command line argument.

hermes x 4 
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 `'.  *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:

  # (condition-case ... . ((nil)))
  # bind (tmsg top frame value message label)
  append-progress-feedback(font-lock "Fontifying .cshrc..." 0 nil)
  # bind (frame value message label)
  display-progress-feedback(font-lock "Fontifying .cshrc..." 0)
  # bind (str)
  # (unwind-protect ...)
  # bind (args value fmt label)
  progress-feedback-with-label(font-lock "Fontifying %s..." 0 ".cshrc")
  # bind (maybe-loudly end beg)
  font-lock-default-unfontify-region(1 7926 t)
  # bind (loudly end beg)
  font-lock-unfontify-region(1 7926 t)
  # bind (was-on font-lock-verbose font-lock-message-threshold aborted)
  # (unwind-protect ...)
  # bind (font-lock-verbose)
  # bind (on-p maximum-size arg)
  # bind (explicit-defaults)
  # bind (nomodes after-find-file-from-revert-buffer noauto warn error)
  after-find-file(nil t)
  byte-code("..." [buffer-file-number number truename buffer-file-truename buf buffer-file-name 
set-buffer-major-mode erase-buffer nil (byte-code "?«?§?Â	?Ã\"?¨?ª?¥?Ä	?Ã\"?¨?Â?§" [rawfile filename 
insert-file-contents-literally t insert-file-contents] 3) ((file-error ...)) abbreviate-file-name 
file-name-directory make-local-variable backup-inhibited t after-find-file find-file-use-truenames default-directory 
backup-enable-predicate rawfile error nowarn] 3)
  # (condition-case ... . ((t (byte-code "?Â!?¨?Ã	@	A\"?§" ... 3))))
  # (unwind-protect ...)
  # bind (error number truename buf rawfile nowarn filename)
  # bind (codesys filename)
  # bind (dir file-count line end-of-options file-p arg tem)
  # bind (command-line-args-left)
  # (condition-case ... . ((t (byte-code "	?Â?§" ... 1))))
  # bind (error-data)
  # (condition-case ... . error)
  # (catch top-level ...)

[1]    Segmentation fault            xemacs (core dumped)
hermes x 4 

I didn't get a core dump but a stackdump.

hermes x 21 cat xemacs-21.4.23.exe.stackdump 
Stack trace:
Frame     Function  Args
00289730  61030F12 (00000378, 0000EA60, 000000A4, 00289790)
00289850  610E514A (6119FE10, 00000000, 00289884, 00000000)
hermes x 22 

Do you have an idea why I get a segmentation fault or do you know
which package I should replace with an older one to get a working
xemacs once more? Thank you very much for any help in advance.

Kind regards


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]