From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Piet van Oostrum Newsgroups: gmane.emacs.devel Subject: Re: Possible memory corruption problem Date: Thu, 16 Feb 2006 14:21:24 +0100 Message-ID: References: <17393.41708.76191.538450@parhasard.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1140116342 4303 80.91.229.2 (16 Feb 2006 18:59:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 16 Feb 2006 18:59:02 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 16 19:59:01 2006 Return-path: 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 1F9oKs-00032o-4O for ged-emacs-devel@m.gmane.org; Thu, 16 Feb 2006 19:58:40 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F9oKr-00026i-JV for ged-emacs-devel@m.gmane.org; Thu, 16 Feb 2006 13:58:37 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F9jSb-0000LN-N5 for emacs-devel@gnu.org; Thu, 16 Feb 2006 08:46:18 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F9jKe-0006x9-Ct for emacs-devel@gnu.org; Thu, 16 Feb 2006 08:38:06 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F9j5b-0004CN-CO for emacs-devel@gnu.org; Thu, 16 Feb 2006 08:22:32 -0500 Original-Received: from [131.211.80.10] (helo=mail.cs.uu.nl) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F9jAj-0005S0-H6 for emacs-devel@gnu.org; Thu, 16 Feb 2006 08:27:49 -0500 Original-Received: from mail.cs.uu.nl (localhost.localdomain [127.0.0.1]) by mail.cs.uu.nl (Postfix) with ESMTP id BD405A3611 for ; Thu, 16 Feb 2006 14:22:29 +0100 (CET) Original-Received: from ordesa.cs.uu.nl (ordesa.cs.uu.nl [131.211.81.146]) by mail.cs.uu.nl (Postfix) with ESMTP id B1106A3602 for ; Thu, 16 Feb 2006 14:22:29 +0100 (CET) Original-Received: by ordesa.cs.uu.nl (Postfix, from userid -2) id BA9882E217E; Thu, 16 Feb 2006 14:21:27 +0100 (CET) Original-Received: from ordesa.cs.uu.nl (localhost [127.0.0.1]) by ordesa.cs.uu.nl (Postfix) with ESMTP id 38A1C2E214D for ; Thu, 16 Feb 2006 14:21:26 +0100 (CET) X-Mailer: emacs 22.0.50.5 (via feedmail 8 I) Original-To: emacs-devel@gnu.org In-Reply-To: (Richard M. Stallman's message of "Tue, 14 Feb 2006 23:39:55 -0500") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (darwin) X-AV-Checked: ClamAV using ClamSMTP at cs.uu.nl X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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:50623 Archived-At: >>>>> "Richard M. Stallman" (RMS) wrote: >RMS> Does this change do the job? (Of course, we would put HAVE_GETRLIMIT >RMS> under the control of configure.) I think under normal circumstances this would generate the warnings. However, man getrlimit in Mac OS X says: RLIMIT_DATA The maximum size (in bytes) of the data segment for a process; this defines how far a program may extend its break with the sbrk(2) system call. I don't know if this is to be taken literally, because as I wrote in a previous message sbrk() isn't used at all. Also I doubt that this will give a warning if the memory shortage is caused by depletion of swap space rather than running out of address space. Moreover I think this patch does not solve the problem at hand, as these are only warnings. My assessment of the situation was that Emacs got an unsuccessful malloc or realloc and didn't notice it. When Emacs gets NULL on these it should abort or some such whether there has been a low memory warning or not, and apparently it just continued. -- Piet van Oostrum URL: http://www.cs.uu.nl/~piet [PGP 8DAE142BE17999C4] Private email: piet@vanoostrum.org