public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/3927] FryskHelpManager initial startup causes backtrace
Date: Mon, 29 Jan 2007 17:10:00 -0000	[thread overview]
Message-ID: <20070129171010.5384.qmail@sourceware.org> (raw)
In-Reply-To: <20070126145142.3927.rmoseley@redhat.com>


------- 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.


  reply	other threads:[~2007-01-29 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26 14:51 [Bug general/3927] New: " rmoseley at redhat dot com
2007-01-29 17:10 ` cagney at redhat dot com [this message]
2007-01-31 21:16 ` [Bug general/3927] " rmoseley at redhat dot com
2007-01-31 21:39 ` cagney at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070129171010.5384.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).