From owner-freebsd-toolchain@FreeBSD.ORG Wed Oct 23 13:10:38 2013 Return-Path: Delivered-To: freebsd-toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 77E7D763; Wed, 23 Oct 2013 13:10:38 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 48BA42D43; Wed, 23 Oct 2013 13:10:37 +0000 (UTC) Received: from [10.60.213.211] (173-13-112-142-NewEngland.hfc.comcastbusiness.net [173.13.112.142]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r9NDATCk051494 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 23 Oct 2013 13:10:30 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: clang sanitizers (memory, address, etc) From: David Chisnall In-Reply-To: <526769DF.5020805@peralex.com> Date: Wed, 23 Oct 2013 14:10:27 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <70880890-4C9F-482E-AF44-0774114320F9@FreeBSD.org> References: <5266780F.70201@peralex.com> <526769DF.5020805@peralex.com> To: squid@peralex.com X-Mailer: Apple Mail (2.1508) Cc: freebsd-toolchain@FreeBSD.org, Dimitry Andric X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 13:10:38 -0000 On 23 Oct 2013, at 07:17, squid@peralex.com wrote: > Thanks. I look forward to that. I'll have a look myself, but I = suspect > the work involved is beyond my skill set. I had a chat with some of the *san people (mostly from Google Moscow) = quite recently. They've refactored most of the code so it should be = fairly obvious where the platform-specific bigs are. In most cases, = it's just some interposition on malloc() and friends, which should be = relatively easy to port. I'd love for us to have this stuff in the base system, and even versions = of the base libraries (and programs) compiled to use them. David