From owner-freebsd-arch@FreeBSD.ORG Fri Apr 11 18:31:21 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ECB30959; Fri, 11 Apr 2014 18:31:21 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A42F61CD9; Fri, 11 Apr 2014 18:31:21 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.8/8.14.8) with ESMTP id s3BIV9jR003967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 11 Apr 2014 11:31:12 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <534834E6.1010206@freebsd.org> Date: Sat, 12 Apr 2014 02:31:02 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: John Baldwin , Warner Losh Subject: Re: Time for turning off gdb by default? Or worse... References: <201404091145.58792.jhb@freebsd.org> <674B7C0B-9235-4030-9A44-7F9984CA2F67@bsdimp.com> <201404101702.52622.jhb@freebsd.org> In-Reply-To: <201404101702.52622.jhb@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2014 18:31:22 -0000 On 4/11/14, 5:02 AM, John Baldwin wrote: > On Thursday, April 10, 2014 4:37:17 pm Warner Losh wrote: >> OK. Here’s the summary of the thread: >> >> (1) gdb in tree is ancient >> (2) kgdb is quite useful, and only in tree >> (3) ports gdb rocks, but… >> (4) ports gdb exists only for a few architectures >> (5) Fixing ptrace will allow us to use a more-stock gdb >> >> Action items: >> >> (1) Create a wiki page with timeline to deactivation and removal. >> (2) Create milestones along the path for >> (a) kgdb + devel/gdb* >> (b) architectural coverage >> (c) ptrace fixes > I would actually invert these. I think (c) is the simplest to do > (in regards to the thread changes I mentioned) and I think it makes (b) > a lot easier to do. > >> (3) profit. > Otherwise, sounds good to me. > >> I’ve done these steps and documented them at https://wiki.freebsd.org/GdbRetirement to allow work to progress (or not) without repeating this discussion. Thanks > for everybody’s feedback. Feel free to comment on the wiki page or edit it for missing items (or testing you’ve done). >> At this point, I’m withdrawing the gdb disabled by default patches. > So one thing we kicked around on IRC is that I think it would be nice > to have some sort of place to collaborate on maintaining useful GPLv3 > toolchain bits. I don't think they belong in the main tree. However, > it might be nice to someday have another SVN repo that can be overlaid > into an existing src checkout (maybe using SVN external references?) > to allow GPLv3 gdb, etc. to be built as part of a world build. > > I don't know that we need an SVN repo on a FreeBSD.org machine right now, > but something would be nice. I have for some time, actively promoted the idea of "base ports vs regular ports" where base ports are not in the tree as such, but we maintain the port as part of the project, and a failure to build a base port is as much a reason to "stop ship" as failure to compile something in the tree..