From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: mem leak Date: Mon, 24 Apr 2006 17:39:36 +0900 Message-ID: References: <34e52d434e5685.34e568534e52d4@net.lu.se> <87y7xv5qv7.fsf@pacem.orebokech.com> Reply-To: Miles Bader NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1145868117 29150 80.91.229.2 (24 Apr 2006 08:41:57 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 24 Apr 2006 08:41:57 +0000 (UTC) Cc: LENNART BORGMAN , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 24 10:41:55 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 1FXwdf-0003nd-LK for ged-emacs-devel@m.gmane.org; Mon, 24 Apr 2006 10:41:47 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FXwdf-0006jl-6V for ged-emacs-devel@m.gmane.org; Mon, 24 Apr 2006 04:41:47 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FXwbe-0005oW-H9 for emacs-devel@gnu.org; Mon, 24 Apr 2006 04:39:42 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FXwbb-0005mC-Rk for emacs-devel@gnu.org; Mon, 24 Apr 2006 04:39:41 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FXwbb-0005lt-8C for emacs-devel@gnu.org; Mon, 24 Apr 2006 04:39:39 -0400 Original-Received: from [203.180.232.82] (helo=mgate02.necel.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FXwdm-0002mF-5J; Mon, 24 Apr 2006 04:41:54 -0400 Original-Received: from relay11.aps.necel.com (relay11 [10.29.19.46]) by mgate02.necel.com (8.13.6/8.13.1) with ESMTP id k3O828Tp018079; Mon, 24 Apr 2006 17:39:36 +0900 (JST) Original-Received: from relay31.aps.necel.com ([10.29.19.20] [10.29.19.20]) by relay11.aps.necel.com with ESMTP; Mon, 24 Apr 2006 17:39:36 +0900 Original-Received: from dhapc248.dev.necel.com ([10.114.97.235] [10.114.97.235]) by relay31.aps.necel.com with ESMTP; Mon, 24 Apr 2006 17:39:36 +0900 Original-Received: by dhapc248.dev.necel.com (Postfix, from userid 31295) id 3B8903E5; Mon, 24 Apr 2006 17:39:36 +0900 (JST) Original-To: Romain Francoise System-Type: i686-pc-linux-gnu Blat: Foop In-Reply-To: (Miles Bader's message of "Mon, 24 Apr 2006 17:26:58 +0900") Original-Lines: 19 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:53311 Archived-At: Miles Bader writes: >>> It prints a warning message, but it tends to get lost among the large >>> amount of other noise that emacs spits out during compilation. >> >> The splash screen shows a warning message when pure space overflowed >> during the build. It's hard to miss. > > ... unless you have the splash screen disabled (as I do) ... :-/ Is there any reason _not_ to make the build fail in this case? As I've found an Emacs with an overflowed pure space is not very usable anyway... so it's something that really should be fixed immediately by the builder if it happens. -miles -- It wasn't the Exxon Valdez captain's driving that caused the Alaskan oil spill. It was yours. [Greenpeace advertisement, New York Times, 25 February 1990]