From ortmann@sparc.isl.net  Mon Sep 15 19:35:49 1997
Received: from watcher.isl.net (ppp27-uunet.infopet.com [208.210.103.29])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA14527
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 15 Sep 1997 19:35:48 -0700 (PDT)
Received: (from ortmann@localhost)
	by watcher.isl.net (8.8.7/8.8.5) id VAA02530;
	Mon, 15 Sep 1997 21:30:40 -0500 (CDT)
Message-Id: <199709160230.VAA02530@watcher.isl.net>
Date: Mon, 15 Sep 1997 21:30:40 -0500 (CDT)
From: Daniel Ortmann <ortmann@sparc.isl.net>
Reply-To: ortmann@sparc.isl.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: cat /proc/*/mem gives "cat: /proc/0/mem: Bad address"
X-Send-Pr-Version: 3.2

>Number:         4551
>Category:       kern
>Synopsis:       cat /proc/*/mem gives "cat: /proc/0/mem: Bad address"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep 15 19:40:00 PDT 1997
>Closed-Date:    Mon Sep 15 21:47:54 PDT 1997
>Last-Modified:  Mon Sep 15 21:48:31 PDT 1997
>Originator:     Daniel Ortmann
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
(not-applicable)
>Environment:

The last ctm update applied was src-cur.3048.gz

>Description:

cat /proc/*/mem >/dev/null produces the following:

cat: /proc/0/mem: Bad address
cat: /proc/1/mem: Bad address
cat: /proc/119/mem: Bad address
cat: /proc/122/mem: Bad address
cat: /proc/125/mem: Bad address
cat: /proc/128/mem: Bad address
cat: /proc/1478/mem: Bad address
cat: /proc/1486/mem: Bad address
cat: /proc/165/mem: Bad address
cat: /proc/1720/mem: Bad address
cat: /proc/1968/mem: Bad address
cat: /proc/2/mem: Bad address
cat: /proc/2040/mem: Bad address
cat: /proc/2041/mem: Bad address
cat: /proc/210/mem: Bad address
cat: /proc/213/mem: Bad address
cat: /proc/214/mem: Bad address
cat: /proc/215/mem: Bad address
cat: /proc/216/mem: Bad address
cat: /proc/217/mem: Bad address
cat: /proc/218/mem: Bad address
cat: /proc/219/mem: Bad address
cat: /proc/220/mem: Bad address
cat: /proc/221/mem: Bad address
cat: /proc/222/mem: Bad address
cat: /proc/223/mem: Bad address
cat: /proc/224/mem: Bad address
cat: /proc/227/mem: Bad address
cat: /proc/27/mem: Bad address
cat: /proc/3/mem: Bad address
cat: /proc/4/mem: Bad address
cat: /proc/67/mem: Bad address
cat: /proc/85/mem: Bad address
cat: /proc/94/mem: Bad address
cat: /proc/98/mem: Bad address
cat: /proc/curproc/mem: Bad address

I expected 

>How-To-Repeat:

cat /proc/*/mem >/dev/null

>Fix:

>Release-Note:
>Audit-Trail:

From: John-Mark Gurney <gurney_j@efn.org>
To: ortmann@sparc.isl.net
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/4551: cat /proc/*/mem gives "cat: /proc/0/mem: Bad address"
Date: Mon, 15 Sep 1997 20:59:59 -0700

 Daniel Ortmann scribbled this message on Sep 15:
 > cat /proc/*/mem >/dev/null produces the following:
 > 
 > cat: /proc/0/mem: Bad address
 
 umm.. isn't this expected at /proc/*/mem is the actually memory, and
 the first page (at least) is usually unmapped)...
 
 > cat: /proc/1/mem: Bad address
 > cat: /proc/119/mem: Bad address
 > cat: /proc/122/mem: Bad address
 > cat: /proc/125/mem: Bad address
 > 
 > I expected 
 
 what did you expect??
 
 > cat /proc/*/mem >/dev/null
 
 just this?? 
 
 -- 
   John-Mark Gurney                          Modem/FAX: +1 541 683 6954
   Cu Networking
 
   Live in Peace, destroy Micro$oft, support free software, run FreeBSD
State-Changed-From-To: open->closed 
State-Changed-By: davidg 
State-Changed-When: Mon Sep 15 21:47:54 PDT 1997 
State-Changed-Why:  

The "bad address" is caused by the first page of a process being 
unreadable. The results are as expected. 
>Unformatted:
