From owner-freebsd-current Thu Oct 17 13: 3:23 2002 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 065E437B401; Thu, 17 Oct 2002 13:03:23 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B5BB43E65; Thu, 17 Oct 2002 13:03:22 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g9HK3LKu019197; Thu, 17 Oct 2002 16:03:21 -0400 (EDT) Date: Thu, 17 Oct 2002 16:03:21 -0400 (EDT) From: Daniel Eischen To: Juli Mallett Cc: audit@FreeBSD.ORG, current@FreeBSD.ORG, Daniel Eischen Subject: Re: I often have orphaned FDs in threaded programs... In-Reply-To: <20021017034126.A45732@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 17 Oct 2002, Juli Mallett wrote: > I have a program which shares a lot of (orphaned) FDs between threads, > and requesting a dump (SIGINFO) results in a core, because the FD owner > si NULL. Here's a diff from my local tree, for review: Actually, fd locking is not enabled anymore so that's why the table has null entries. I would recommend just deleting the printing of the owner altogether. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message