From owner-freebsd-arch@freebsd.org Thu Jul 21 09:26:44 2016 Return-Path: Delivered-To: freebsd-arch@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 1961DB9F278 for ; Thu, 21 Jul 2016 09:26:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D50471FA3; Thu, 21 Jul 2016 09:26:43 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bQAFX-000PbY-4e; Thu, 21 Jul 2016 12:26:35 +0300 Date: Thu, 21 Jul 2016 12:26:35 +0300 From: Slawa Olhovchenkov To: John Baldwin Cc: freebsd-arch@freebsd.org Subject: Re: Retiring in-tree GDB Message-ID: <20160721092635.GN20831@zxy.spb.ru> References: <2678091.es0AGJQ0Ou@ralph.baldwin.cx> <4450836.nX37FfBzNy@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4450836.nX37FfBzNy@ralph.baldwin.cx> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 09:26:44 -0000 On Wed, Jul 20, 2016 at 12:00:21PM -0700, John Baldwin wrote: > On Tuesday, October 20, 2015 01:36:28 PM John Baldwin wrote: > > When this topic was last raised (by Warner I believe), the primary objection > > (certainly my main one) was that the in-tree kgdb was the only kernel debugger > > available. kgdb is now available via the devel/gdb port in ports (and as of > > last week was enabled by default, so 'pkg install gdb' will get you a kgdb > > binary). The kgdb in ports is in general superior to the one in the base > > system. It is a cross debugger by default (and with my pending patches to > > libkvm it even supports cross debugging of vmcores). > > > > There are some issues still with devel/gdb: namely it does not currently > > support some of the platforms supported by our in tree gdb such as arm and > > mips. For these platforms I think the in-tree gdb will need to remain until > > there is a suitable alternative. > > > > However, I would like to propose that we retire the in-tree GDB for some of > > our platforms (namely x86) for 11. In particular, I think we should default > > to enabling lldb and disabling gdb for platforms that meet the following > > criteria: > > > > 1) devel/gdb works including thread and kgdb support > > 2) lldb works > > > > We could perhaps be more aggressive and handle lldb and gdb toggles > > independently, but I think we want to ship some sort of userland debugger > > out of the box on all of our platforms. The question I think might be if > > we end up with platforms where 1) is true but 2) is not (such as powerpc). > > > > I believe that these conditions are only true for x86 currently. > > > > Comments? > > I believe I've fixed the one last thing that was depending on /usr/bin/gdb > (crashinfo) to use devel/gdb if it is present. I'd either like to disable > the base gdb on amd64 in the next week or so on HEAD, or perhaps if people are > really gutsy, disable it for all platforms on HEAD. We still don't have kgdb > in ports for non-x86 (though for ppc at least kgdb in ports and base is > equally dysfunctional). > > However, to start with: > > 1) Does anyone have a reason to keep /usr/bin/gdb on amd64? > > 2) Does anyone have a reason to keep /usr/bin/gdb on !amd64? lldb replace /usr/bin/gdb? lldb still bundled with base system?