From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5730 invoked by alias); 29 Jan 2007 17:10:27 -0000 Received: (qmail 5385 invoked by uid 48); 29 Jan 2007 17:10:10 -0000 Date: Mon, 29 Jan 2007 17:10:00 -0000 Message-ID: <20070129171010.5384.qmail@sourceware.org> From: "cagney at redhat dot com" To: frysk-bugzilla@sourceware.org In-Reply-To: <20070126145142.3927.rmoseley@redhat.com> References: <20070126145142.3927.rmoseley@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/3927] FryskHelpManager initial startup causes backtrace X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00184.txt.bz2 List-Id: ------- Additional Comments From cagney at redhat dot com 2007-01-29 17:10 ------- I think I know whats happening, and wow, that means frysk's core is being pretty agressive! - the desktop thread calls frysk.sys.Fork.daemon which: does a vfork as the first step in creating a daemon, and then does a waitpid on the child - meanwhile the core thread sees the SIGCHLD for that same waitpid and grabs it - this leaves the desktop process's waitpid with nothing to wait for, hence the error That means the core is going to need to directly handle the child create, and the help code just request it. As a way of confirming this, try using: frysk.proc.Host.requestCreateAttachedProc (String[] args, null) i.e., no observer. It should create the process and then immediatly detach from it. Perhaps a: frysk.proc.Host.requestCreateDaemonProc (String[] args) should be added. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |cagney at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=3927 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.