From owner-freebsd-current Sun Feb 4 13:10:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (unknown [213.162.128.50]) by hub.freebsd.org (Postfix) with ESMTP id 2C7D637B491 for ; Sun, 4 Feb 2001 13:10:29 -0800 (PST) Received: by mimer.webgiro.com (Postfix, from userid 66) id 6728B2DC0B; Sun, 4 Feb 2001 22:16:52 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id C50147817; Sun, 4 Feb 2001 22:11:33 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id C0C6210E1C for ; Sun, 4 Feb 2001 22:11:33 +0100 (CET) Date: Sun, 4 Feb 2001 22:11:33 +0100 (CET) From: Andrzej Bialecki To: freebsd-current@freebsd.org Subject: Broken procfs/status, related to kthreads Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Whoever made procfs aware of kernel threads broke also the /proc/%pid/status line. Or, maybe it's a by-product of showing kthreads in the proc table... According to procfs(5), the status line contains several well-defined fields separated by spaces. However, the kernel thread names look like 'swi5: task queue' and 'swi1: net', which results in variable number of space-separated fields. As a consequence, some software that parses this line gives incorrect results. I noticed this while trying to fix mysterious coredumps in src/release/picobsd/tinyware/aps (which is obsolete anyway, but it should work). Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message