From owner-cvs-all  Tue Sep 15 14:47:17 1998
Return-Path: <owner-cvs-all>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA13979
          for cvs-all-outgoing; Tue, 15 Sep 1998 14:47:17 -0700 (PDT)
          (envelope-from owner-cvs-all)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13903;
          Tue, 15 Sep 1998 14:46:55 -0700 (PDT)
          (envelope-from jdp@FreeBSD.org)
From: John Polstra <jdp@FreeBSD.ORG>
Received: (from jdp@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id OAA01213;
	Tue, 15 Sep 1998 14:46:35 -0700 (PDT)
Date: Tue, 15 Sep 1998 14:46:35 -0700 (PDT)
Message-Id: <199809152146.OAA01213@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject: cvs commit: src/sys/kern imgact_elf.c
Sender: owner-cvs-all@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

jdp         1998/09/15 14:46:35 PDT

  Modified files:
    sys/kern             imgact_elf.c 
  Log:
  Instead of just the data and stack segments, include all writable
  segments (except memory-mapped devices) in the ELF core file.  This
  is really nice.  You get access to the data areas of all shared
  libraries, and even to files that are mapped read-write.
  
  In the future, it might be good to add a new resource limit in the
  spirit of RLIMIT_CORE.  It would specify the maximum sized writable
  segment to include in core dumps.  Segments larger than that would
  be omitted.  This would be useful for programs that map very large
  files read/write but that still would like to get usable core dumps.
  
  Revision  Changes    Path
  1.32      +199 -68   src/sys/kern/imgact_elf.c