Date: Wed, 19 Apr 2017 14:13:06 -0500 From: Justin Hibbits <jrh29@alumni.cwru.edu> To: rgrimes@freebsd.org Cc: John Baldwin <jhb@freebsd.org>, Slawa Olhovchenkov <slw@zxy.spb.ru>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, src-committers <src-committers@freebsd.org> Subject: Re: svn commit: r317094 - head/share/mk Message-ID: <CAHSQbTCF_JAkubQuBi=9nDVr79KjpLnbCMhjjSW1J9n1gDchcg@mail.gmail.com> In-Reply-To: <201704191633.v3JGXWmu031427@pdx.rh.CN85.dnsmgr.net> References: <1709565.BYcnqjiFaR@ralph.baldwin.cx> <201704191633.v3JGXWmu031427@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 19, 2017 at 11:33 AM, Rodney W. Grimes <freebsd@pdx.rh.cn85.dnsmgr.net> wrote: >> On Wednesday, April 19, 2017 01:28:37 AM Slawa Olhovchenkov wrote: >> > On Tue, Apr 18, 2017 at 12:45:25PM -0700, John Baldwin wrote: >> > >> > > On Tuesday, April 18, 2017 07:30:13 PM Slawa Olhovchenkov wrote: >> > > > On Tue, Apr 18, 2017 at 04:27:48PM +0000, John Baldwin wrote: >> > > > >> > > > > Author: jhb >> > > > > Date: Tue Apr 18 16:27:48 2017 >> > > > > New Revision: 317094 >> > > > > URL: https://svnweb.freebsd.org/changeset/base/317094 >> > > > > >> > > > > Log: >> > > > > Disable in-tree GDB by default on x86, mips, and powerpc. >> > > > > >> > > > > GDB in ports contains all of the functionality as GDB in base >> > > > > (including kgdb) for these platforms along with additional >> > > > > functionality. In-tree GDB remains enabled on ARM and sparc64. >> > > > > GDB in ports does not currently support kernel debugging on arm, >> > > > > and ports GDB for sparc64 has not been tested (though it does >> > > > > include sparc64 support). >> > > > > >> > > > > Reviewed by: bdrewery, emaste, imp >> > > > > Relnotes: yes >> > > > > Sponsored by: DARPA / AFRL >> > > > > Differential Revision: https://reviews.freebsd.org/D10399 >> > > > >> > > > Generating core.txt now complety broken? >> > > >> > > No. crashinfo has supported gdb from ports for quite a while now. >> > > If you 'pkg install gdb' crashinfo defaults to using the ports gdb over >> > > the base one already. >> > >> > I am about clean install, w/o ports. >> >> Until we get some sort of klldb support that will not work. However, >> we already have platforms now where /usr/bin/gdb doesn't work for that. >> riscv and aarch64 aren't supported in ancient gdb, and the MIPS >> /usr/bin/gdb didn't really work for me in my testing. > > So we break what worked on a Tier1 Platform? With my "user" hat on > these are the exact kind of breakages that send me looking for another > platform to run on. We far to often just go oh you can do X y and Z > to get around what we broke forgetting that the user 6 months from now > when this hits a release isnt gona come ask, he may just go down the > road to something else. > > Remove gdb WHEN klldb can replace it, not a day before. Using "oh its > broken on aarch64 and mips" is not a reason to break things on i386/amd64. > It's not removed, it's disabled by default now. As the commit message states, gdb in ports is much more feature filled than gdb in base > Yes, I know we want to get gnu stuff out of the tree, but that needs > to come AFTER a proper replacement is avaliable. > >> >> > Also, how to generate core.txt after crash, reboot and install gdb >> > from ports? (port instaled after crash) >> >> You can always run crashinfo by hand. > > /me starts to look for a new OS, this one is not very good at user support. I'd say this more warrants a set of "blessed" packages to include on install disks so we get this functionality without the extra step. - Justin > > > -- > Rod Grimes rgrimes@freebsd.org >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHSQbTCF_JAkubQuBi=9nDVr79KjpLnbCMhjjSW1J9n1gDchcg>