From owner-freebsd-arch@FreeBSD.ORG Tue Apr 8 21:24:57 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 816B6EE2 for ; Tue, 8 Apr 2014 21:24:57 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask.apl.washington.edu", Issuer "troutmask.apl.washington.edu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4469B1739 for ; Tue, 8 Apr 2014 21:24:57 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.8/8.14.8) with ESMTP id s38LOa4e075453 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 8 Apr 2014 14:24:36 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.8/8.14.8/Submit) id s38LOZuq075452; Tue, 8 Apr 2014 14:24:35 -0700 (PDT) (envelope-from sgk) Date: Tue, 8 Apr 2014 14:24:35 -0700 From: Steve Kargl To: Warner Losh Subject: Re: Time for turning off gdb by default? Or worse... Message-ID: <20140408212435.GA75404@troutmask.apl.washington.edu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-arch 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: Tue, 08 Apr 2014 21:24:57 -0000 On Tue, Apr 08, 2014 at 02:34:35PM -0600, Warner Losh wrote: (courtesy line wrap to something well below 80 characters) > The gdb in the tree seems to be of very limited usefulness > these days. It doesn?t seem to work on clang-enabled > architectures w/o building -gdwarf-2, it doesn?t seem to work > with threaded applications, and on some architectures it > doesn?t seem to work at all (mips comes to mind, but it may > have been the two binaries I tried). > (patch removed) > to the tree, which will turn gdb off by default. It may make > more sense to just remove it entirely, but I?m not sure I want > to go there just yet in case there are things that I?m missing. > I believe that the port will be adequate for all architectures > we support, but haven?t tested this directly yet. I do know > that on amd64, the port just worked, where the in-tree gdb > was an epic fail. I suppose the obvious questions are: 1) Is lldb ready for prime time? 2) What effect does this have on kgdb? Note, /sys/conf/NOTES contains #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols Should this be updates to DEBUG=-gdwarf-2? PS: You'll need to sweep src/ for references to gdb(1). -- Steve