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. > 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. -- John Baldwin _______________________________________________ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"