From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!not-for-mail
From: "Richard M. Stallman" <rms@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: allocate_string_data memory corruption
Date: Tue, 24 Jan 2006 11:46:34 -0500
Message-ID: <E1F1RJS-0000YP-SK@fencepost.gnu.org>
References: <87vewha2zl.fsf@stupidchicken.com>
	<E1Ezkqz-0008VZ-CM@fencepost.gnu.org>
	<m14q3zy2wf.fsf-monnier+emacs@gnu.org>
	<E1F05Ck-0005Pd-KH@fencepost.gnu.org>
	<87zmlq6w62.fsf-monnier+emacs@gnu.org>
	<87u0bw6wwz.fsf-monnier+emacs@gnu.org>
	<272681AE-627E-4FDF-BD16-246D423524AC@gnu.org>
Reply-To: rms@gnu.org
NNTP-Posting-Host: main.gmane.org
Content-Type: text/plain; charset=ISO-8859-15
X-Trace: sea.gmane.org 1138123200 28846 80.91.229.2 (24 Jan 2006 17:20:00 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Tue, 24 Jan 2006 17:20:00 +0000 (UTC)
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 24 18:19:58 2006
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane.org
Original-Received: from lists.gnu.org ([199.232.76.165])
	by ciao.gmane.org with esmtp (Exim 4.43)
	id 1F1Rno-000789-3a
	for ged-emacs-devel@m.gmane.org; Tue, 24 Jan 2006 18:17:56 +0100
Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43)
	id 1F1RqV-0004a9-AW
	for ged-emacs-devel@m.gmane.org; Tue, 24 Jan 2006 12:20:43 -0500
Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1F1RMJ-0006GV-2z
	for emacs-devel@gnu.org; Tue, 24 Jan 2006 11:49:31 -0500
Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1F1RMH-0006Ey-Q6
	for emacs-devel@gnu.org; Tue, 24 Jan 2006 11:49:30 -0500
Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1F1RMH-0006Ec-GK
	for emacs-devel@gnu.org; Tue, 24 Jan 2006 11:49:29 -0500
Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1F1RRD-0001F4-VX
	for emacs-devel@gnu.org; Tue, 24 Jan 2006 11:54:36 -0500
Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34)
	id 1F1RJS-0000YP-SK; Tue, 24 Jan 2006 11:46:34 -0500
Original-To: Ken Raeburn <raeburn@gnu.org>
In-reply-to: <272681AE-627E-4FDF-BD16-246D423524AC@gnu.org> (message from Ken
	Raeburn on Sun, 22 Jan 2006 19:35:03 -0500)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Xref: news.gmane.org gmane.emacs.devel:49482
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/49482>

    It may just push the memory corruption from the Lisp object pool to  
    the malloc pool, since malloc isn't safe for signal handlers either.   

Yes it is; malloc uses BLOCK_INPUT.