Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Apr 2014 15:43:08 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc:        freebsd-arch <freebsd-arch@freebsd.org>
Subject:   Re: Time for turning off gdb by default? Or worse...
Message-ID:  <57ECB078-3D7A-4BE8-AA29-1ED7BB347DBD@bsdimp.com>
In-Reply-To: <20140408212435.GA75404@troutmask.apl.washington.edu>
References:  <DD38131E-9A43-4EFA-A27D-ED6B64F6A35A@bsdimp.com> <20140408212435.GA75404@troutmask.apl.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

On Apr 8, 2014, at 3:24 PM, Steve Kargl =
<sgk@troutmask.apl.washington.edu> wrote:

> On Tue, Apr 08, 2014 at 02:34:35PM -0600, Warner Losh wrote:
>=20
> (courtesy line wrap to something well below 80 characters)
>=20
>> 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).
>>=20
>=20
> (patch removed)
>=20
>> 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.
>=20
> I suppose the obvious questions are:
>=20
> 1) Is lldb ready for prime time?

Doesn=92t matter.

> 2) What effect does this have on kgdb?  Note, /sys/conf/NOTES contains

Unfortunately, kgdb isn=92t available as a port, so that does matter. It =
is one thing arguing against this change.

> #makeoptions	DEBUG=3D-g		#Build kernel with gdb(1) debug =
symbols
>=20
> Should this be updates to DEBUG=3D-gdwarf-2?

Nope. It should stay exactly as it is. We convert -g to -gdwarf-2 for =
those compilers that need it.

> PS: You'll need to sweep src/ for references to gdb(1).

No. It is just not built by default, not being kicked out of the tree.

Warner




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57ECB078-3D7A-4BE8-AA29-1ED7BB347DBD>