Add gdb report from jhb

This commit is contained in:
Benjamin Kaduk 2015-10-17 22:42:26 +00:00
parent c7b649a8f7
commit dd6497b338
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=47609

View file

@ -2452,4 +2452,68 @@
</body>
</project>
<project cat='bin'>
<title>Updates to GDB</title>
<contact>
<person>
<name>
<given>John</given>
<common>Baldwin</common>
</name>
<email>jhb@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="https://reviews.FreeBSD.org/D3341">Extend libkvm to
support cross-debugging of vmcores</url>
</links>
<body>
<p>Support for following children after forks for &os; was implemented and
merged upstream to GDB's master branch, and was included in GDB
7.10.</p>
<p>Work has continued on porting <tt>kgdb</tt> to newer
<tt>gdb</tt>. The amd64, i386, powerpc, powerpc64, and sparc64
backends have all been ported and are now available via a new
<tt>KGDB</tt> option in the devel/gdb port.</p>
<p>The MD backends for libkvm have been rewritten to support
cross-debugging crashdumps, and the <tt>kgdb</tt> targets for
amd64 and i386 have been reworked to support cross-debugging.
Both i386 and amd64 kgdb binaries have been able to cross-debug
the other architecture's vmcores with these changes. This
changeset for libkvm is not yet in the tree, but is awaiting more
testing.</p>
</body>
<help>
<task>
<p>Test the libkvm changes on platforms other than amd64, i386,
and powerpc64.</p>
</task>
<task>
<p>Figure out why the powerpc kgdb targets are not able to unwind
the stack past the initial frame.</p>
</task>
<task>
<p>Add support for more platforms (arm, mips, aarch64) to
upstream gdb for both userland and kgdb.</p>
</task>
<task>
<p>Write a new 1:1-only thread target for &os; that can be
sent upstream.</p>
</task>
<task>
<p>Add support for debugging powerpc vector registers.</p>
</task>
</help>
</project>
</report>