From owner-freebsd-current@freebsd.org Mon Jun 26 05:45:04 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A41CBDA20A7 for ; Mon, 26 Jun 2017 05:45:04 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 81BC56715D for ; Mon, 26 Jun 2017 05:45:03 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:54002] helo=localhost) by dnvrco-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 50/A5-03935-85F90595; Mon, 26 Jun 2017 05:44:57 +0000 Date: Mon, 26 Jun 2017 05:44:52 +0000 Message-ID: <50.A5.03935.85F90595@dnvrco-omsmta01> From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: Ports still broken by ino64? References: <78.25.03057.F5ADD495@dnvrco-omsmta02> <89.F1.03057.D331E495@dnvrco-omsmta02> X-RR-Connecting-IP: 107.14.64.6:25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Mon, 26 Jun 2017 05:45:04 -0000 from Adrian Chadd: > valgrind broke as part of the ino64 work :( Valgrind was not on my mind! Your post sent me to ls -d /usr/ports/*/val* to find valgrind, and then read the pkg-descr. One less tool for getting debugging information when something crashes? Tom