Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 9 Apr 2014 00:26:29 +0300
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Warner Losh <imp@bsdimp.com>
Cc:        freebsd-arch <freebsd-arch@freebsd.org>
Subject:   Re: Time for turning off gdb by default? Or worse...
Message-ID:  <20140408212629.GD21331@kib.kiev.ua>
In-Reply-To: <DD38131E-9A43-4EFA-A27D-ED6B64F6A35A@bsdimp.com>
References:  <DD38131E-9A43-4EFA-A27D-ED6B64F6A35A@bsdimp.com>

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

--2W4Na7kn/Mq3HLmY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 08, 2014 at 02:34:35PM -0600, Warner Losh wrote:
> Greetings,
>=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 architect=
ures it doesn?t seem to work at all (mips comes to mind, but it may have be=
en the two binaries I tried).
>=20
> It seems like we?d be doing our users a favor by applying:
>=20
> diff -r 8bfca9de870e share/mk/bsd.own.mk
> --- a/share/mk/bsd.own.mk
> +++ b/share/mk/bsd.own.mk
> @@ -266,7 +266,6 @@ WITH_HESIOD=3D
>      FREEBSD_UPDATE \
>      GAMES \
>      GCOV \
> -    GDB \
>      GNU \
>      GNU_GREP_COMPAT \
>      GPIB \
> @@ -355,6 +354,7 @@ WITH_HESIOD=3D
>      CLANG_EXTRAS \
>      CTF \
>      DEBUG_FILES \
> +    GDB \
>      HESIOD \
>      INSTALL_AS_USER \
>      LLDB \
>=20
> to the tree, which will turn gdb off by default. It may make more sense t=
o 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 ade=
quate for all architectures we support, but haven?t tested this directly ye=
t. I do know that on amd64, the port just worked, where the in-tree gdb was=
 an epic fail.
>=20
> Comments?

Do we need kgdb ?
Do we need a debugger that is aware of our signal frames which are not
annotated with the dwarf ?

I personally need and use this.  I also use standalone build of the stock
gdb.  Both in-tree gdb/kgdb and stock gdb are incommutable (for me).

--2W4Na7kn/Mq3HLmY
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQIcBAEBAgAGBQJTRGmEAAoJEJDCuSvBvK1BXGkP/3e5CRas+yyrWYfnUBHlA00J
/a0V4VFexVOj/IATSn0i4NqGO+iF7KHy3SFaq290YB11KYUg22poNHw0Klx/jK7C
4Sp7FF2FNN4Js0nuGSK+gHRLchU36X+6rKNviC6G2WVTovZ4H+RuEkHDxD/GkYtp
5j6viibiTutntAGExCLe0LyJQpvdRmnp9eJ+TNM2nH6EehY9fcET01RqpYY1SZMn
T99uwHrcxyHsrDGLe0o6+KS7OaJqs0BhsVUtbFbCAHB0mcZMV4RaDiyysfGcinp+
hHjGC+uEJLz2hKzyQHw6RUsS1ncw8apASFA1GPeFblvDV9TzbxDiGPItYtEOslv3
urhd2d2QE4kH+o2DbKBwmIg2q647ADzKGAUE8uWuJcgShwHiV6hO4jWZY+dH72sJ
a+UF784Vb6HUWBG0KvsAKC/hFcXaD+oggLdAnYlpQ4Uz7bwzTnDZ2h7FNoK4hXBv
H0VIn/aMHI44AAaidrA1VSS5b8phgppLw5En+GoT2iUhi12P67hz0ADsG2NhmCvA
YH0YkrpvqKk889IpVKHF+NnP/Zu2w7uACmYW/32+Y96JpINInZ5dBhfszEKiUiG2
GSOjpPGySMk0jzfTx2jHaLfRhyawEFV2tCjzNd2QIS0HbA26r94izM2V9IIFkrKe
EgMUw9ZVOVvKeBOovQXu
=grSe
-----END PGP SIGNATURE-----

--2W4Na7kn/Mq3HLmY--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140408212629.GD21331>