From owner-freebsd-current@FreeBSD.ORG Fri Jan 13 20:18:31 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C745C16A41F; Fri, 13 Jan 2006 20:18:31 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78D8543D48; Fri, 13 Jan 2006 20:18:31 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 22DE51A3C25; Fri, 13 Jan 2006 12:18:31 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 18E4152740; Fri, 13 Jan 2006 15:18:30 -0500 (EST) Date: Fri, 13 Jan 2006 15:18:29 -0500 From: Kris Kennaway To: Giorgos Keramidas Message-ID: <20060113201829.GA24887@xor.obsecurity.org> References: <1A89617A-5F0E-492E-8C21-10A4F679BCD2@freebsd.org> <14547.1137178334@critter.freebsd.dk> <20060113195319.GA17963@flame.pc> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <20060113195319.GA17963@flame.pc> User-Agent: Mutt/1.4.2.1i Cc: Poul-Henning Kamp , freebsd-current@freebsd.org, Jason Evans Subject: Re: HEADSUP: malloc changeover X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2006 20:18:31 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 13, 2006 at 09:53:19PM +0200, Giorgos Keramidas wrote: > On 2006-01-13 19:52, Poul-Henning Kamp wrote: > >In message <1A89617A-5F0E-492E-8C21-10A4F679BCD2@freebsd.org>, Jason Eva= ns writes: > >> The most likely types of application bugs that this malloc > >> implementation will uncover are: > > > > And speaking from experience: You can do Jason a big favour by > > trying your app with Electric Fence or similar before yelling > > at him. >=20 > HEH! Definitely. I have built & run at least four versions > since January 11, two with DEBUG_FLAGS=3D'-g' for both userland and > kernel and two without. As Jason said, we should probably keep > looking for potential problems both in the new malloc() and the > programs that use it, but the fact that my laptop still runs > quite fine with several dozens of ports installed some time back > in December seems to imply there aren't any _really_ _nasty_ bugs > in malloc so far There are several ports that have build failures due to application bugs. I think I emailed some of the maintainers already, but there are more that are going to be (re-)exposed by some more recent changes than that patchset I was testing. Kris --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDyAsVWry0BWjoQKURApAVAJ9RwOufazuHZ4EKOc/As4vMrGu/vQCg0eAt RazlJAE+lxfUUot/wACe8l0= =d6+O -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l--