From owner-cvs-sys  Sun May 11 18:01:33 1997
Return-Path: <owner-cvs-sys>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA20893
          for cvs-sys-outgoing; Sun, 11 May 1997 18:01:33 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA20887;
          Sun, 11 May 1997 18:01:26 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id KAA16219; Mon, 12 May 1997 10:57:58 +1000
Date: Mon, 12 May 1997 10:57:58 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199705120057.KAA16219@godzilla.zeta.org.au>
To: bde@freebsd.org, dfr@nlsystems.com
Subject: Re: cvs commit:  src/sys/i386/i386 machdep.c
Cc: cvs-all@freebsd.org, CVS-committers@freebsd.org, cvs-sys@freebsd.org
Sender: owner-cvs-sys@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>What exactly is BDE_DEBUGGER?  I have seen references to it in the sources
>for *years* and I always wondered what it was and whether it would be a
>useful thing to have.

It is my low level x86 debugger.  Under 386BSD and FreeBSD I used it to
debug the boot blocks, kernel startup and general kernel things before
ddb was ported to 386BSD.  ddb is better for general kernel things except
it is sloppy about disabling interrupts so interrupt handlers can be hard
to debug.  I haven't used my debugger in the kernel for a year or two :-).

Bruce