From owner-freebsd-ports@FreeBSD.ORG Wed May 7 15:22:50 2008 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D5BB1065677; Wed, 7 May 2008 15:22:50 +0000 (UTC) (envelope-from rnoland@2hip.net) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 515DF8FC0A; Wed, 7 May 2008 15:22:50 +0000 (UTC) (envelope-from rnoland@2hip.net) Received: from [192.168.166.46] ([70.168.41.2]) (authenticated bits=0) by gizmo.2hip.net (8.13.8/8.13.8) with ESMTP id m47EmPYM090940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 May 2008 10:48:25 -0400 (EDT) (envelope-from rnoland@2hip.net) From: Robert Noland To: Jeremy Chadwick In-Reply-To: <20080507143004.GA59170@eos.sc1.parodius.com> References: <20080506053244.GA94936@eos.sc1.parodius.com> <20080507143004.GA59170@eos.sc1.parodius.com> Content-Type: text/plain Organization: 2Hip Networks Date: Wed, 07 May 2008 10:48:16 -0400 Message-Id: <1210171696.30323.2.camel@squirrel.corp.cox.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on gizmo.2hip.net Cc: ports@freebsd.org, amistry@am-productions.biz, Matt Subject: Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2008 15:22:50 -0000 On Wed, 2008-05-07 at 07:30 -0700, Jeremy Chadwick wrote: > On Wed, May 07, 2008 at 09:19:24AM -0500, Matt wrote: > > Sorry - should have been more specific than the generic "stuck" > > description. Top shows the process state as "fu_msg" and it is not > > consuming any processor resources, just seemingly sits there idling. > > Output from ps is: > > > > UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND > > 1000 4019 1 0 44 0 6324 2528 - Ts ?? 0:00.00 > > /usr/local/libexec//gvfs-fuse-daemon /home/mtosto > > The "T" flag under State says that the process is stopped. It's as if > the process was running in the foreground, and was ^Z'd -- same > behaviour. I don't want to state the obvious, but attaching to the process with gdb will produce the stopped state. Was this ps snap taken before or after attaching with gdb? robert. > The part which confuses me (I'm sure others can explain this part) is > that the parent PID is 1, which is init. This would indicate that the > process is actually a zombie whose parent has been killed off, and the > child's parent has been assigned to init. > > You might try doing a "kill -CONT" on the process to see what happens. > > I don't think truss or ktrace are going to help here, because something > is explicitly stopping the process (SIGSTOP or some other means). >