Date: Tue, 8 Apr 2014 14:34:35 -0600 From: Warner Losh <imp@bsdimp.com> To: freebsd-arch <freebsd-arch@freebsd.org> Subject: Time for turning off gdb by default? Or worse... Message-ID: <DD38131E-9A43-4EFA-A27D-ED6B64F6A35A@bsdimp.com>
next in thread | raw e-mail | index | archive | help
Greetings,
The gdb in the tree seems to be of very limited usefulness these days. =
It doesn=92t seem to work on clang-enabled architectures w/o building =
-gdwarf-2, it doesn=92t seem to work with threaded applications, and on =
some architectures it doesn=92t seem to work at all (mips comes to mind, =
but it may have been the two binaries I tried).
It seems like we=92d be doing our users a favor by applying:
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 \
to the tree, which will turn gdb off by default. It may make more sense =
to just remove it entirely, but I=92m not sure I want to go there just =
yet in case there are things that I=92m missing. I believe that the port =
will be adequate for all architectures we support, but haven=92t tested =
this directly yet. I do know that on amd64, the port just worked, where =
the in-tree gdb was an epic fail.
Comments?
Warner=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DD38131E-9A43-4EFA-A27D-ED6B64F6A35A>