Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Jul 2002 17:34:50 +1000 (EST)
From:      Bruce Evans <bde@zeta.org.au>
To:        Peter Wemm <peter@wemm.org>
Cc:        "Greg 'groggy' Lehey" <grog@FreeBSD.org>, "David E. O'Brien" <obrien@FreeBSD.org>, <cvs-committers@FreeBSD.org>, <cvs-all@FreeBSD.org>
Subject:   Re: No kgdb? (was: cvs commit: src/gnu/usr.bin/binutils/gdb kvm-fbsd.c)
Message-ID:  <20020701165404.N7024-100000@gamplex.bde.org>
In-Reply-To: <20020701003235.84908390F@overcee.wemm.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 30 Jun 2002, Peter Wemm wrote:

> "Greg 'groggy' Lehey" wrote:
> > On Saturday, 29 June 2002 at 21:47:43 -0700, David E. O'Brien wrote:
> > > obrien      2002/06/29 21:47:43 PDT
> > >
> > >   Modified files:
> > >     gnu/usr.bin/binutils/gdb kvm-fbsd.c
> > >   Log:
> > >   Dike out bits specific to i386.  This pretty much means no kgdb for
> > >   non-i386 platforms.
> >
> > Can you give more details here?  Was there support for kgdb on other
> > platforms before you did this?  What about previous versions of gdb?
> > What's needed to get the support?
>
> Yes and no.  With the old compiler and old gdb, we had alpha and i386 support.
> gcc-3 broke gdb completely, so we had no support at all (userland or kernel)
> after that.  Now, we have i386 kgdb support and there are works-in-progress
> for other platforms.
>
> This has been explained at great detail on the lists.  There really wasn't
> any need to drag it up yet again here.

To drag it out a bit more ... I tried using the old gdb on a simple
program to see how much the new gdb has broken "info float".  The old
gdb worked fine and the new gdb had most of the bugs that I expected
(*) (**).  The old gdb doesn't work on a not so-simple program
(/bin/cat) compiled with -g, but works on at least /bin/cat compiled
with -gdwarf (-gdwarf2 gives the same breakage as -g, and -gstabs gives
SIGBUS instead of stopping at a breakpoint at main()).

(*) various cosmetic bugs, and lost printing of the exception status word.
(**) lost printing of the prompt after suspend/resume.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020701165404.N7024-100000>