From owner-freebsd-hackers Wed Dec 3 12:12:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09158 for hackers-outgoing; Wed, 3 Dec 1997 12:12:31 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA09152 for ; Wed, 3 Dec 1997 12:12:28 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.7) with ESMTP id MAA05798; Wed, 3 Dec 1997 12:12:02 -0800 (PST) (envelope-from jdp) Message-Id: <199712032012.MAA05798@austin.polstra.com> To: jbryant@unix.tfs.net cc: freebsd-hackers@freebsd.org Subject: Re: emacs core dumping on -current? In-reply-to: Your message of "Wed, 03 Dec 1997 14:05:15 CST." <199712032005.OAA19354@unix.tfs.net> Date: Wed, 03 Dec 1997 12:12:01 -0800 From: John Polstra Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 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