From owner-freebsd-commit  Wed Jan 24 10:30:16 1996
Return-Path: owner-commit
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA10395
          for freebsd-commit-outgoing; Wed, 24 Jan 1996 10:30:16 -0800 (PST)
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA10360
          for cvs-all-outgoing; Wed, 24 Jan 1996 10:29:53 -0800 (PST)
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA10346
          for cvs-sys-outgoing; Wed, 24 Jan 1996 10:29:35 -0800 (PST)
Received: (from peter@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA10334
          Wed, 24 Jan 1996 10:29:25 -0800 (PST)
Date: Wed, 24 Jan 1996 10:29:25 -0800 (PST)
From: Peter Wemm <peter>
Message-Id: <199601241829.KAA10334@freefall.freebsd.org>
To: CVS-committers, cvs-sys
Subject: cvs commit: src/sys/kern sys_process.c
Sender: owner-commit@FreeBSD.ORG
Precedence: bulk

peter       96/01/24 10:29:21

  Modified:    sys/kern  sys_process.c
  Log:
  Major fixes for ptrace()...
  
  PT_ATTACH/PT_DETACH implemented now and fully operational.
  PT_{GET|SET}{REGS|FPREFS} implemented now, using code shared with procfs
  PT_{READ|WRITE}_{I|D} now uses code shared with procfs
  ptrace opcodes now fully permission checked, including ownerships.
  doing an operation to the u-area on a swapped process should no longer
  panic.
  running gdb as root works for me now, where it didn't before.
  general cleanup..
  
  Note, that this has some tightening of permissions/access checks etc.
  Some of these may be going too far..  In particular, the "owner" of the
  traced process is enforced.  The process that created or attached to
  the traced process is now the only one that can "do" things to it.
  
  Revision  Changes    Path
  1.21      +226 -99   src/sys/kern/sys_process.c