From owner-freebsd-hackers Wed Dec 3 13:11:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA13368 for hackers-outgoing; Wed, 3 Dec 1997 13:11:06 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA13356 for ; Wed, 3 Dec 1997 13:11:00 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.7) with SMTP id NAA24428; Wed, 3 Dec 1997 13:10:55 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Wed, 3 Dec 1997 13:10:54 -0800 (PST) From: Chris Timmons To: John Polstra cc: jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: emacs core dumping on -current? In-Reply-To: <199712032012.MAA05798@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk just out of curiosity, is the core file size a nice round number like say 16777216? I've been surprised at times by login.conf limits... -c On Wed, 3 Dec 1997, John Polstra wrote: > > looking through your notes, could this be a problem with > > gnu-malloc() which emacs defaults to? > > Toward the end of the build process, emacs does this hack where it > loads all the standard elisp files and compiles them internally. Then > it "dumps" itself to produce the executable that gets installed. > I.e., it writes its own address space out to a file and hacks it into > an a.out executable. > > The problem has something to do with that. I can't look into it any > deeper until this evening at the soonest. > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth >