From owner-cvs-src@FreeBSD.ORG Sat Jan 14 21:34:21 2006 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20D7816A420; Sat, 14 Jan 2006 21:34:21 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A02D43D45; Sat, 14 Jan 2006 21:34:19 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (patr530-a141.otenet.gr [212.205.215.141]) by aiolos.otenet.gr (8.13.4/8.13.4/Debian-8) with ESMTP id k0ELYGGM023267; Sat, 14 Jan 2006 23:34:16 +0200 Received: by flame.pc (Postfix, from userid 1001) id B8EA011608; Sat, 14 Jan 2006 23:32:38 +0200 (EET) Date: Sat, 14 Jan 2006 23:32:38 +0200 From: Giorgos Keramidas To: Jason Evans Message-ID: <20060114213238.GA15253@flame.pc> References: <200601121809.k0CI9QGV028693@repoman.freebsd.org> <20060112182804.GA1047@flame.pc> <20060113012900.GA16082@flame.pc> <554CC8A8-35FB-424A-B883-505C26ECBBE8@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <554CC8A8-35FB-424A-B883-505C26ECBBE8@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/stdlib malloc.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2006 21:34:21 -0000 On 2006-01-13 11:07, Jason Evans wrote: >On Jan 12, 2006, at 5:29 PM, Giorgos Keramidas wrote: >> >> [...] >> >> Does this look like an off-by-one error to you too Jason? >> Apparently, the allocated size of s->data is s->size, which is 873 >> bytes, but then Emacs tries to access s->data[873]. >> >> Does it look like I'm right in thinking that this is a bug in Emacs? > > This looks like a bug in emacs, as you say, but I don't know if it > has any particular relation to the posix_memalign() changes. Apparently it does seem related to posix_memalign() changes. When I bootstrap Emacs without posix_memalign(), by manually tweaking src/config.h after configure runs, and #undef POSIX_MEMALIGN, then it passes the bootstrap stage normally. > If updating to either before or after the broken > posix_memalign() revision, and need help figuring out the > issue, please let me know. More issues come up after updating to today's CURRENT version of malloc. In particular: irssi started core dumping with symptoms similar to those of Emacs bootstrap, i.e. access to memory regions that are in gdb xorg-server-snap is a requirement in FreeBSD/amd64, but it seems to trigger a panic and an insta-reboot with an ATI Radeon here. Since this is the laptop I'm also using for every day work, I'll try to revert back to the cvs -D '2006/01/12 07:28:20 UTC' version for now. Apart from looking at the source code, do we have some sort of 'design' docs for the new malloc(), to see if I can help debug these problems a bit more when I restore my laptop's ports & packages from the backup later tonight? - Giorgos