From owner-freebsd-current@FreeBSD.ORG Sun Feb 20 21:50:32 2005 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 3CD2716A4CE for ; Sun, 20 Feb 2005 21:50:32 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D29043D2F for ; Sun, 20 Feb 2005 21:50:31 +0000 (GMT) (envelope-from caelian@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so185815rnf for ; Sun, 20 Feb 2005 13:50:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=szSh8UwyCnE9hpp1C9Y7Z17PYWL43UM301SRQYgeneuI34jzRj7yjc9mW3ZywfKkJWrTag76Xv+Bk5KyQK8Y7asUhco/v4qCnqsy5xKH0XAZ26wh70F8CbOmCdXS7wMzPRZttpt1P9xUjGtMxxNJC1dHdQLzpAnM8TB5rrlTBSI= Received: by 10.38.163.31 with SMTP id l31mr62561rne; Sun, 20 Feb 2005 13:50:31 -0800 (PST) Received: by 10.38.89.69 with HTTP; Sun, 20 Feb 2005 13:50:31 -0800 (PST) Message-ID: Date: Sun, 20 Feb 2005 13:50:31 -0800 From: Pascal Hofstee To: FreeBSD Current Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: GNUstep and libkvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pascal Hofstee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Feb 2005 21:50:32 -0000 A while ago i initiated a thread on hackers@ requesting additional information regarding a known issue with the gnustep-gui port "needing /proc" even when gnustep-base itself (which in turn is used by -gui) was compiled without procfs support. The results of my findings can be found in the following list-archive entries: http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg49357.html http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg49577.html Short summary is the kvm_getargv function seems to trigger a kvm_uread call when the length of "command + argumentlist" exceeds the value of kern.ps_arg_cache_limit. This kvm_uread call is responsible for the observed /proc groveling. I had hoped to acquire some additional information on how to properlly debug libkvm in GDB and if this /proc dependency is intended behavior. To me personally (though i am not a kernel hacker) it doens't really make sense to have libkvm (which is intended to be a 'replacement' for /proc to my understanding) intenrally depend on the same system it's trying to 'replace', though I noticed from the manpages that the kvm_getargv function doesn't really belong in libkvm. Can anybody at least either confirm wether or not this is - intended behavior - a bug and a proper PR should likely be created For those interested i have put up a small "kvmtest" testcase that basically contains the GNUstep code that triggers this behaviour for easier debugging. This tarball is available at http://netherite.student.utwente.nl/~daeron/kvmtest.tar.gz Any feedback regarding this issue would be highly appreciated. With kind regards, Pascal Hofstee