Re: GDB - do we dare?

From: David O'Brien <obrien_at_FreeBSD.org>
Date: Sun, 13 Jul 2003 16:49:12 -0700
On Sat, Jul 12, 2003 at 01:05:00PM +0200, Mark Kettenis wrote:
>    Date: Fri, 11 Jul 2003 15:50:02 -0700
>    From: Marcel Moolenaar <marcel_at_xcllnt.net>
> 
>    Gang,
> 
>    With the gcc(1) dust not even settled yet, I like to get some feedback
>    on gdb(1). AFAICT, this is the deal:
> 
>    o  Both ia64 and amd64 need gdb(1) support before they can become a
>       tier 1 platform. I think this implies upgrading to 5.3 the least.
> 
> Upgrading to 5.3 for amd64 won't really help.  While 5.3 included
> support for amd64, I'm told it is seriously broken.  Since then, I've
> almost completely reworked GDB's amd64 target, to bring it in line
> with the i386 target, and adapt it to some major architectural changes
> in GDB.  Based on that work, I've finished a FreeBSD/amd64 port
> yesterday.  I'll try to get it on GDB's 6.0 release branch.  However,
> backporting it to 5.3 would be a major PITA and IMHO a tremendous
> waste of effort.

Not sure about that.  I wish you would touch base with SuSE.  AMD has had
SuSE do quite a lot of work to make GDB 5.3 very usable on AMD64.  I know
there are parts of the work SuSE has yet to send to the GDB lists.  I am
worried that FreeBSD's AMD64 bits will be too different from the Linux
ones and FreeBSD won't be able to leverage the work AMD is paying SuSE to
do.

That said, giving the amount of work it takes to import a GDB
release(snapshot) and get it working in our tree -- we really should
import a 6.0 snapshot.

However, FreeBSD/sparc64 isn't properly supported in FSF GDB either.
When Jason Thorpe added NetBSD/sparc64 support he did it very NetBSD
specific rather than do it in a more general BSD/sparc64 way that all the
BSD's could leverage.  Generalizing his bits is needed in the FSF GDB
bits.


> I'm not really familliar with the support for debugging FreeBSD
> kernels in GDB since that support is not in the FSF tree.  Is there
> any chance that this code will be contributed back?

Probably not, but I'd love it if you would take a look at it -- the
times I've talked about to GDB guys hasn't been encouraging.  How can we
work to get the bits in /usr/src/gnu/usr.bin/binutils/gdb made part of
stock FSF GDB (along with our diffs from the FSF vendor branch in
/usr/src/contrib/gdb)?


> This would involve a copyright assignment, which could prove to be a
> major obstacle.

We (I) can work to address this issue.

> A2 I'm volunteering to help out here.  As the i386 target maintainer
>    and FreeBSD host/native maintainer, I seem to have sufficient
>    background in GDB I guess ;-).  For almost two years now, I've been
>    using FreeBSD/i386 as my primary (development) platform, and I hope
>    at least some people have noticed that the upstream GDB works much
>    better on FreeBSD/i386 and FreeBSD/Alpha now.  Now that I've got it
>    working on FreeBSD/amd64, I'll give FreeBSD/ia64 a shot.

Others may hate me for this, but getting stock GDB working on sparc64 is
of higher priority as it is a Tier-1 platform and we have more sparc64
users than ia64.  Or maybe, you can help back me on the gdb-patches
mailing list and I can revive Jake's and my patches for sparc64.

>    releases, I'm dedicated to FreeBSD, and I'm certainly willing to do
>    work on integrating new versions of GDB into the FreeBSD tree.

I'm more than willing to mentor you what it takes to do a GDB import into
FreeBSD.

Enjoy!
-- 
-- David  (obrien_at_FreeBSD.org)
Received on Sun Jul 13 2003 - 14:49:21 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:15 UTC