From xemacs-m  Sun Aug 17 13:55:10 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id NAA22520
	for <xemacs-beta@xemacs.org>; Sun, 17 Aug 1997 13:55:09 -0500 (CDT)
Received: (from steve@localhost)
	by altair.xemacs.org (8.8.6/8.8.6) id LAA07869;
	Sun, 17 Aug 1997 11:59:48 -0700
Mail-Copies-To: never
To: xemacs-beta@xemacs.org
Subject: Re: reproducable seg fault crash - edebugging font-lock code.
References: <87vi14zshe.fsf@bittersweet.inetarena.com> <m2203s20oo.fsf@altair.xemacs.org> <rxslo20k8o6.fsf@ecf.teradyne.com>
X-Face: `'%\i;ySOu]g?NlziJSk_$&@]KP`}~PEQPjZ5;nxSaDW_o$4+4%Ab]%Ifw3ZR;7TIT3,O,'
 @2{L;]ox6kc;$_5kU'n**9vFg-]eV~GbxSVCx|(s%uR[],*:^WKmC`B}(;|k9/m]gwt?&`t;^rfCJg
 khHH>pP1W\)xM0U@!FNDD72{3fDP$PkBhx^7Z?-WxH6DbFN:QOnT`llzW}VGdYv;n9lzljQvKTIBhQ
 YuV
X-Attribution: sb
From: SL Baur <steve@xemacs.org>
In-Reply-To: Adrian Aichner's message of "17 Aug 1997 19:42:49 +0200"
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Date: 17 Aug 1997 11:59:47 -0700
Message-ID: <m2rabszlcs.fsf@altair.xemacs.org>
Lines: 30
X-Mailer: Gnus v5.4.64/XEmacs 20.3(beta19) - "Kiev"

[Your example blows the stack away]

Adrian Aichner <aichner@ecf.teradyne.com> writes:

> Here is ...
> [2 edebug-crash.el <application/octet-stream>]
> (load-library (concat data-directory "sample.emacs"))

Lovely.  It doesn't crash if I load my .emacs instead.  So that
probably means either EFS or lazy-good-for-nothing-lock.  Let me
check ...

Yup.  Commenting out the enabling of lazy-good-for-nothing-lock
eliminates the crash.

--- /usr/src/xemacs-20.0/etc/sample.emacs       Thu May 22 18:35:57 1997
+++ ./sample.emacs      Sun Aug 17 11:54:18 1997
@@ -565,7 +565,7 @@
 ;;; accurate as using full font-lock or fast-lock, but it's *much*
 ;;; faster.  No more annoying pauses when you load files.
 
-(add-hook 'font-lock-mode-hook 'turn-on-lazy-lock)
+;(add-hook 'font-lock-mode-hook 'turn-on-lazy-lock)
 ;; I personally don't like "stealth mode" (where lazy-lock starts
 ;; fontifying in the background if you're idle for 30 seconds)
 ;; because it takes too long to wake up again on my piddly Sparc 1+.


I have no interest in tracking down problems with that package, but
someone else might.

