From owner-cvs-sys  Thu Nov 20 10:13:41 1997
Return-Path: <owner-cvs-sys>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA22869
          for cvs-sys-outgoing; Thu, 20 Nov 1997 10:13:41 -0800 (PST)
          (envelope-from owner-cvs-sys)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA22564;
          Thu, 20 Nov 1997 10:09:48 -0800 (PST)
          (envelope-from bde@FreeBSD.org)
From: Bruce Evans <bde@FreeBSD.ORG>
Received: (from bde@localhost)
	by freefall.freebsd.org (8.8.6/8.8.5) id KAA13434;
	Thu, 20 Nov 1997 10:09:37 -0800 (PST)
Date: Thu, 20 Nov 1997 10:09:37 -0800 (PST)
Message-Id: <199711201809.KAA13434@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-sys@FreeBSD.ORG
Subject: cvs commit: src/sys/i386/i386 db_interface.c
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

bde         1997/11/20 10:09:37 PST

  Modified files:
    sys/i386/i386        db_interface.c 
  Log:
  Fixed write enabling of the kernel text section.  The overlap
  checking was mostly wrong at the boundaries.  For the lower limit,
  VM_MIN_KERNEL_ADDRESS was used instead of btext and there was an
  off-by-(`size' - 1) error.  For the upper limit, &etext was used
  instead of etext and there was an off-by-1 error.  The bugs were
  harmless because `size' is not too large and some memory is mapped
  just beyond the ends.  We still depend on the former to avoid
  having to handle the case where the memory range covers the whole
  text section, and on the latter to prevent problems when we map
  just beyond an end to allow writing an address range that overlaps
  the end.
  
  Fixed placement of a nearby comment.
  
  Revision  Changes    Path
  1.38      +5 -7      src/sys/i386/i386/db_interface.c