From owner-freebsd-current@FreeBSD.ORG Wed Oct 22 13:47:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37FA416A4B3 for ; Wed, 22 Oct 2003 13:47:00 -0700 (PDT) Received: from pd6mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 189EC43FAF for ; Wed, 22 Oct 2003 13:46:59 -0700 (PDT) (envelope-from bondc@shaw.ca) Received: from pd2mr2so.prod.shaw.ca (pd2mr2so-ser.prod.shaw.ca [10.0.141.109])2003))freebsd-current@freebsd.org; Wed, 22 Oct 2003 14:37:35 -0600 (MDT) Received: from pn2ml6so.prod.shaw.ca (pn2ml6so-qfe0.prod.shaw.ca [10.0.121.150]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTP id <0HN600GCEEMNLA@l-daemon> for freebsd-current@freebsd.org; Wed, 22 Oct 2003 14:37:35 -0600 (MDT) Received: from muscle (h24-80-125-94.vf.shawcable.net [24.80.125.94]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with SMTP id <0HN600ECBEMMTL@l-daemon> for freebsd-current@freebsd.org; Wed, 22 Oct 2003 14:37:35 -0600 (MDT) Date: Wed, 22 Oct 2003 13:45:11 -0700 From: Chris Bond To: freebsd-current@freebsd.org Message-id: <000901c398dd$6310ddf0$0100a8c0@muscle> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailer: Microsoft Outlook Express 6.00.2800.1158 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal Subject: struct kinfo_proc->ki_tsize is inaccurate X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Oct 2003 20:47:00 -0000 Greetings, When I use kvm_getprocs() together with KERN_PROC_PID to get process information, the structure it returns contains an inaccurate ki_tsize (text segment size) variable. On my machine, it seems to alternate--seemingly at random--between 1 and 168, neither of which is correct. The process in question is suspended when I make the call (ptrace(PT_TRACE_ME...)). Just wondering what the deal is. Chris