Results 1 to 3 of 3

Thread: xemacs crashes with syntax highlighting

  1. #1

    Default xemacs crashes with syntax highlighting

    opensuse 13.2 64 bit.
    distro version of xemacs (21.5.34)

    If I enable syntax highlighting in a buffer it crashes. Seems 100% reproducible on bash and perl.
    I worked fine on opensuse 13.1 which I think had the same xemacs version.

    Does anyone have any ideas? Is xemacs dead? Should I bin it along with my open toe-d sandals?
    Sadly it is (was) so powerful I cannot find another editor that replaces its functionality.
    Kate looks pretty good and upto date, but no keyboard macros, no align-regexp function,
    no man page viewing...
    Sigh.

    Any fixes greatly appreciated! Thank in advance...

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,851

    Default Re: xemacs crashes with syntax highlighting

    Quote Originally Posted by jonb62 View Post

    If I enable syntax highlighting in a buffer it crashes. Seems 100% reproducible on bash and perl.
    I worked fine on opensuse 13.1 which I think had the same xemacs version.
    This happens in a bash session? Then any chance that you copy/past what happens in between CODE tags (the # button in the tool ba of the post editor) in a post here? That probably will give more information to others then a simple "it crashes".
    Henk van Velden

  3. #3

    Default Re: xemacs crashes with syntax highlighting

    Quote Originally Posted by hcvv View Post
    This happens in a bash session? Then any chance that you copy/past what happens in between CODE tags (the # button in the tool ba of the post editor) in a post here? That probably will give more information to others then a simple "it crashes".
    Here 'tis...

    Code:
    jonb@monster:~> xemacs
    Warning: Missing charsets in String to FontSet conversion
    
    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 that won't work, send ordinary
    email to `xemacs-beta@xemacs.org'.  *MAKE SURE* to include this entire
    output from this crash, especially including the Lisp backtrace, as well as
    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 reoccurrence of the crash.                                                                                                
                                                                                                                                                
    Lisp backtrace follows:                                                                                                                     
                                                                                                                                                
      # (unwind-protect ...)                                                                                                                    
      # (unwind-protect ...)                                                                                                                    
      # bind (inhibit-quit)                                                                                                                     
      # (unwind-protect ...)                                                                                                                    
      # (unwind-protect ...)                                                                                                                    
      # (unwind-protect ...)                                                                                                                    
      # (unwind-protect ...)                                                                                                                    
      # (unwind-protect ...)                                                                                                                    
      # (unwind-protect ...)                                                                                                                    
      # (unwind-protect ...)                                                                                                                    
      # (unwind-protect ...)                                                                                                                    
      redisplay-frame(#<x-frame "XEmacs" on #<x-device on ":0.0" 0x2> 0x2>)                                                                     
      # bind (ext gutter-string val inhibit-read-only frame value message)                                                                      
      raw-append-progress-feedback("Fontifying backup..." 0 #<x-frame "XEmacs" on #<x-device on ":0.0" 0x2> 0x2>)                               
      # bind (tmsg top frame value message label)                                                                                               
      append-progress-feedback(font-lock "Fontifying backup..." 0 nil)                                                                          
      # bind (frame value message label)                                                                                                        
      display-progress-feedback(font-lock "Fontifying backup..." 0)                                                                             
      # bind (str)                                                                                                                              
      # (unwind-protect ...)                                                                                                                    
      # bind (args value fmt label)                                                                                                             
      progress-feedback-with-label(font-lock "Fontifying %s..." 0 "backup")                                                                     
      # bind (maybe-loudly end beg)                                                                                                             
      font-lock-default-unfontify-region(1 3979 t)
      # bind (loudly end beg)
      font-lock-unfontify-region(1 3979 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()
      (progn (font-lock-mode) (customize-set-variable (quote font-lock-mode) font-lock-mode))
      eval((progn (font-lock-mode) (customize-set-variable (quote font-lock-mode) font-lock-mode)))
      # (condition-case ... . error)
      # (catch top-level ...)
    
    Segmentation fault
    thanks...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •