From xemacs-m  Wed Feb 12 01:36:07 1997
Received: from venus.Sun.COM (venus.Sun.COM [192.9.25.5])
	by xemacs.org (8.8.5/8.8.5) with SMTP id BAA27899
	for <xemacs-beta@xemacs.org>; Wed, 12 Feb 1997 01:36:05 -0600 (CST)
Received: from Eng.Sun.COM ([129.146.1.25]) by venus.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id XAA23170; Tue, 11 Feb 1997 23:35:33 -0800
Received: from kindra.eng.sun.com by Eng.Sun.COM (SMI-8.6/SMI-5.3)
	id XAA03130; Tue, 11 Feb 1997 23:35:33 -0800
Received: from xemacs.eng.sun.com by kindra.eng.sun.com (SMI-8.6/SMI-SVR4)
	id XAA03759; Tue, 11 Feb 1997 23:35:31 -0800
Received: by xemacs.eng.sun.com (SMI-8.6/SMI-SVR4)
	id XAA02846; Tue, 11 Feb 1997 23:35:29 -0800
Date: Tue, 11 Feb 1997 23:35:29 -0800
Message-Id: <199702120735.XAA02846@xemacs.eng.sun.com>
From: Martin Buchholz <mrb@Eng.Sun.COM>
To: Steven L Baur <steve@miranova.com>
Cc: xemacs-beta@xemacs.org
Subject: Re: Bug: stack overflow crash
In-Reply-To: <m2ohdqo93s.fsf@altair.xemacs.org>
References: <199702120521.VAA02726@xemacs.eng.sun.com>
	<m2ohdqo93s.fsf@altair.xemacs.org>
Reply-To: Martin Buchholz <mrb@Eng.Sun.COM>
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII

>>>>> "sb" == Steven L Baur <steve@miranova.com> writes:

sb> Martin Buchholz writes:
>> The following extract from reproduce-bugs.el crashes an older version
>> of XEmacs 20.0.  A recent patch fixes this crash, but the behavior is
>> incorrect - a buffer-read-only error should be signalled and the
>> buffer left unchanged.  Instead the operation completes normally,
>> despite buffer-read-only being t.

>> (ignore-errors
>> (encode-coding-region (point-min) (point-max) 'euc-japan))

sb> It will signal if you don't (ignore-errors ...) on it.  I don't
sb> understand what the problem is.

The point is that after running this bit of elisp, the buffer should
contain latin-1 characters.  I see it containing Japanese characters.
It is true that when the (ignore-errors) wrapper is removed, you get a
buffer-read-only error, but the buffer actually did get modified by
the encoding operation.  Perhaps barf-if-buffer-read-only is being
called too late?

Martin

