From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Dave Love Newsgroups: gmane.emacs.bugs Subject: Re: 21.2 startup crash on Irix Date: 19 Apr 2002 18:42:18 +0100 Sender: bug-gnu-emacs-admin@gnu.org Message-ID: References: <8361-Sat13Apr2002105856+0300-eliz@is.elta.co.il> <1429-Wed17Apr2002075325+0300-eliz@is.elta.co.il> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1019238329 29100 127.0.0.1 (19 Apr 2002 17:45:29 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 19 Apr 2002 17:45:29 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16ycRs-0007ZF-00 for ; Fri, 19 Apr 2002 19:45:29 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16ycRl-00013w-00; Fri, 19 Apr 2002 13:45:21 -0400 Original-Received: from djlvig.dl.ac.uk ([148.79.112.146]) by fencepost.gnu.org with smtp (Exim 3.34 #1 (Debian)) id 16ycOw-0000wd-00 for ; Fri, 19 Apr 2002 13:42:27 -0400 Original-Received: from fx by djlvig.dl.ac.uk with local (Exim 3.12 #1 (Debian)) id 16ycOq-0002SX-00; Fri, 19 Apr 2002 18:42:20 +0100 Original-To: Eli Zaretskii Original-Lines: 16 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1.95 Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:804 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:804 "Eli Zaretskii" writes: > Since I wrote that, Gerd installed a change (on RC as well), so you > can have it with "cvs up". I attach the diffs for the release branch > below. I don't see how that can be the problem since it didn't change between 21.1 and 21.2, which is when the lossage occurred. If there's a problem fixing the address range with mmap, you can still use the first arg of mmap as a hint and see if the mapping is done there. [I'm sure it would be better to use DL malloc to replace gmalloc and use that more generally rather than worrying about explicit mmaps there.]