From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chip Coldwell Newsgroups: gmane.emacs.devel Subject: Re: seg-fault in unexelf.c Date: Sat, 22 Jul 2006 08:37:52 -0400 (Eastern Daylight Time) Message-ID: References: <17601.29278.738547.379915@kahikatea.snap.net.nz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Trace: sea.gmane.org 1153571896 26612 80.91.229.2 (22 Jul 2006 12:38:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 22 Jul 2006 12:38:16 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 22 14:38:12 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 1G4GkF-0005pG-75 for ged-emacs-devel@m.gmane.org; Sat, 22 Jul 2006 14:38:11 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G4GkE-0003wG-Qo for ged-emacs-devel@m.gmane.org; Sat, 22 Jul 2006 08:38:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G4Gjx-0003wB-Ri for emacs-devel@gnu.org; Sat, 22 Jul 2006 08:37:53 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G4Gjw-0003vz-Vd for emacs-devel@gnu.org; Sat, 22 Jul 2006 08:37:53 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G4Gjw-0003vw-Ph for emacs-devel@gnu.org; Sat, 22 Jul 2006 08:37:52 -0400 Original-Received: from [66.187.233.31] (helo=mx1.redhat.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G4GkZ-0001a7-UP for emacs-devel@gnu.org; Sat, 22 Jul 2006 08:38:32 -0400 Original-Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k6MCbphw012210; Sat, 22 Jul 2006 08:37:51 -0400 Original-Received: from mail.boston.redhat.com (mail.boston.redhat.com [172.16.76.12]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k6MCbpSd001921; Sat, 22 Jul 2006 08:37:51 -0400 Original-Received: from chiptop (vpn-248-21.boston.redhat.com [10.13.248.21]) by mail.boston.redhat.com (8.12.8/8.12.8) with ESMTP id k6MCboRT016797; Sat, 22 Jul 2006 08:37:50 -0400 Original-To: Nick Roberts In-Reply-To: <17601.29278.738547.379915@kahikatea.snap.net.nz> 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:57472 Archived-At: On Sat, 22 Jul 2006, Nick Roberts wrote: > > I regularly build on FC5 without optimization and don't have any problems > (although I haven't done "make bootstrap for a while, the final build uses > "./temacs -l loadup -batch dump"). Which version? If you mean 21.4 (the one that ships with FC5), then all this means is that, for whatever reason, your kernel is aways setting up the temacs process with a contiguous address space. The fact that the Linux kernel could set up a process virtual address space with holes in it has to be dealt with anyway. Although I must admit, a poll of all the vm-gurus in the building couldn't come up with a good reason *why* you would want a discontiguous process address space. Chip -- Charles M. "Chip" Coldwell Senior Software Engineer Red Hat, Inc 978-392-2426