DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type; q=dns; s=default; b=isVSGsY2LwVgotpa
	q2fI3430k52N4ELgP3k7w9hSO7GR+z8Qs+Ex/mlXxIuczaAwdJnzGg5p+41Tb4Ab
	10w3A9mnsp7QH6IozCFS3N6w0fuHeVsx8lMDIUaHhqgAq0Gu7kc9b8SDqNQ4Qle1
	+l9y2bgAQX9kyjW1hkBZfuHq11c=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: Vin Shelton <acs AT xemacs DOT org>
Subject: Re: xemacs crash when fontifying files
Date: Fri, 13 Feb 2015 09:42:15 -0500
Lines: 37
Message-ID: <871tltzxdk.fsf@alumni.princeton.edu>
References: <slrnmdqd3c DOT 2p3 DOT varro AT anukis DOT local>
Mime-Version: 1.0
Content-Type: text/plain


Will Parsons writes:
> I've recently noticed that xemacs will crash if one attempts to turn on
> syntax highlighting via turn-on-font-lock (even started with the -q option),
> but only if run under X.  (If X is not running, there is no problem.)  The
> crash causes the following to print:
>
> 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 recdabas.c..." 0 nil)
>   # bind (frame value message label)
>   display-progress-feedback(font-lock "Fontifying recdabas.c..." 0)
>...
> Segmentation fault (core dumped)
>
>
> Although I don't use XEmacs a lot, I do have it configured as the editor to
> use for entering configuration control check-in messages, so I think the
> problem must be fairly recent or I would have noticed it before.
>
> (If this problem is better posted to the Cygwin-xfree list, let me know and
> I'll post it there.)

As Volker posted, there's a workaround for this:

(setq progress-feedback-use-echo-area t)


Is this with 21.4.23?  There is a patch in 21.4.23 specifically designed
to work around this.

Thanks,
  Vin


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple