zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>,
	Clint Adams <clint@zsh.org>
Cc: <zsh-workers@sunsite.dk>, <100336-forwarded@bugs.debian.org>,
	<debian-hppa@lists.debian.org>, <joy@debian.org>
Subject: Re: hppa problems
Date: Mon, 11 Jun 2001 05:50:16 +0000	[thread overview]
Message-ID: <1010611055016.ZM22011@candle.brasslantern.com> (raw)
In-Reply-To: <Pine.SV4.4.33.0106110928540.18037-100000@itsrm2.mow.siemens.ru>

On Jun 11,  9:35am, Andrej Borsenkow wrote:
}
} 3. There is an obvious race condition here (between call to sigsuspend and
} child exit).

No, there's no race condition.  These two lines:

    sigfillset(&set);
    sigprocmask(SIG_SETMASK, &set, 0);

mean that SIGCHLD is blocked (along with all other blockable signals).
The sigsuspend() then should unblock SIGCHLD and either wait for the
child to exit, or immediately allow the signal to be delivered if the
child has exited already, and then return.  The test is in part trying
to demonstrate that the implicit race-resolution in this block/suspend
pair does in fact resolve the race.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


      reply	other threads:[~2001-06-11  5:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-10 11:07 PATCH: config.{guess,sub} upgrade Clint Adams
2001-06-10 12:10 ` hppa problems Clint Adams
2001-06-10 16:34   ` Bart Schaefer
2001-06-10 23:10     ` Clint Adams
2001-06-11  0:19       ` Clint Adams
2001-06-11  3:04         ` Bart Schaefer
2001-06-11 13:59           ` Clint Adams
2001-06-11  5:35         ` Andrej Borsenkow
2001-06-11  5:50           ` Bart Schaefer [this message]

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=1010611055016.ZM22011@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=100336-forwarded@bugs.debian.org \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --cc=clint@zsh.org \
    --cc=debian-hppa@lists.debian.org \
    --cc=joy@debian.org \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).