This is the mail archive of the
frysk-bugzilla@sourceware.org
mailing list for the frysk project.
[Bug general/3927] FryskHelpManager initial startup causes backtrace
- From: "cagney at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: frysk-bugzilla at sourceware dot org
- Date: 29 Jan 2007 17:10:10 -0000
- Subject: [Bug general/3927] FryskHelpManager initial startup causes backtrace
- References: <20070126145142.3927.rmoseley@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- 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.