Date: Thu, 22 Aug 2019 09:41:18 -0700 From: John Baldwin <jhb@FreeBSD.org> To: Conrad Meyer <cem@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r351368 - head/sys/gdb Message-ID: <718d767b-7bb3-8e10-f9b5-b696642ad24b@FreeBSD.org> In-Reply-To: <201908220034.x7M0YBOw088032@repo.freebsd.org> References: <201908220034.x7M0YBOw088032@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/21/19 5:34 PM, Conrad Meyer wrote: > Author: cem > Date: Thu Aug 22 00:34:11 2019 > New Revision: 351368 > URL: https://svnweb.freebsd.org/changeset/base/351368 > > Log: > gdb(4): Implement qXfer:threads:read > > This streams out an XML document over several GDB packets describing all > threads in the system; their ids, name, and any loosely defined "extra info" > we feel like including. For now, I have included a string version of the run > state, similar to some of the DDB logic to stringify thread state. > > The benefit of supporting this in addition to the qfThreadInfo/qsThreadInfo > packing is that in this mode, the host gdb does not ask for every thread's > "qThreadExtraInfo," saving per-thread round-trips on "info threads." > > To use this feature, (k)gdb needs to be built with the --with-expat option. > I would encourage enabling this option by default in our GDB port, if it is > not already. FYI, it is as the 'catch syscall' bits also depend on this. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?718d767b-7bb3-8e10-f9b5-b696642ad24b>