From xemacs-m  Mon Aug 25 10:28:48 1997
Received: from wfdutilgw.ml.com (wfdutilf01.ml.com [206.3.74.31])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id KAA14475
	for <xemacs-beta@xemacs.org>; Mon, 25 Aug 1997 10:28:47 -0500 (CDT)
Received: from ml1.ml.com ([199.201.57.130])
	by wfdutilgw.ml.com (8.8.5/8.8.5/MLgw-3.03) with ESMTP id LAA17768
	for <xemacs-beta@xemacs.org>; Mon, 25 Aug 1997 11:23:12 -0400 (EDT)
Received: from commpost.ml.com (commpost.ml.com [146.125.4.24])
	by ml1.ml.com (8.8.5/8.8.5/MLml4-2.07) with SMTP id LAA27050
	for <xemacs-beta@xemacs.org>; Mon, 25 Aug 1997 11:28:16 -0400 (EDT)
Received: from spssunp.spspme.ml.com (spssunp.spspme.ml.com [192.168.111.13]) by commpost.ml.com (8.6.12/8.6.12) with ESMTP id LAA11386 for <xemacs-beta@xemacs.org>; Mon, 25 Aug 1997 11:33:23 -0400
Received: by spssunp.spspme.ml.com (SMI-8.6/SMI-4.1)
	id LAA26033; Mon, 25 Aug 1997 11:28:12 -0400
To: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Re: stack overflow in regexp
References: <199708242214.SAA18232@dolphin.automatrix.com>
X-Face: ByE+UMAp1klWR3?\RNGx(A-~Ri!YT%C6M!sxoJL+.;9`Q/|+dj7[KR>gGMyV.2qZeot0NI`4\MA^_Qg`F9=+Ox&zaE?Y9dV%F~Xzf';Zyk2Aobs.uu^Ey0_C6^~q';G#$HkA!ZAHXPpG-"*|Dd*Z4U$4y{{aI0c%75}i~Of(jxYtI[uIpYF<*Zoe|\*/ufb
X-Y-Zippy: I always wanted a NOSE JOB!!
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Colin Rafferty <craffert@ml.com>
Date: 25 Aug 1997 11:28:12 -0400
In-Reply-To: Skip Montanaro's message of "Sun, 24 Aug 1997 18:14:36 -0400 (EDT)"
Message-ID: <ocrzpq6mgdv.fsf@ml.com>
Lines: 18
X-Mailer: Gnus v5.4.65/XEmacs 20.3(beta18) - "Bratislava"

Skip Montanaro writes:

> In a large compilation buffer I frequently get stack overflow errors when
> executing next-error.  Here's a backtrace:

> To reproduce, execute M-x compile true RET, then replace the compilation
> buffer with the attached file (after uncompressing it).

By the way, this fails on the first line (the 4855 character `pydepend'), 
so the rest of the *compilation* buffer is redundant.  I think that it
is just choking on the size of the line.

The way that compile.el builds up its regular expressions is naive.  You 
might want to play with `compilation-error-regexp-systems-list' to
reduce the matches to only what your system generates.

-- 
Colin

