X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=qvc/Zx
	AainV6WPUYCPyBYKNmWKes7JTP+XonrhsBaV1qTGLTdCHtAGYz3aVVtGEo1jLM8q
	IGXYduDnLVwl3hMdlCe5/lV4JGC+cvS+Oez62OaxZI+5NjvtbWXkd4M46uMWfPQU
	d3wH0czgsE+/WC8WkbUbwjGIeOpoZntgTkUoo=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; s=default; bh=TNAv+25zAObZ
	dezChEC00UukBlA=; b=BmOijJsnC1DqKAVm37xkJB3n2xO7Yz5E0YUogTGOo4Um
	BwjPP7hYDuZ2NzNC4NZDhbdFVzyELFhMeSdxmo2Dvh8vlsHYJXEq0hPriA17qRtX
	ekRnswkOEytmvAO61tdub1glfI/OLtOPUNV/hRpJJBNoyLb4LP/UsEB6W3EOwaE=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=recorded, listing, interest
X-HELO:	lb2-smtp-cloud8.xs4all.net
Date:	Mon, 15 Jul 2019 11:53:58 +0200
Message-ID:	<77b8a5c1a1217fbec1e771f0a5f1ac6c@smtp-cloud8.xs4all.net>
From:	Houder <houder AT xs4all DOT nl>
Reply-To:	cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
Subject:	Re: sigpending() incorrectly returns signals pending on other threads
References:	<CAJouXQne09R+j+k+ZNw5fsZTFqDG5_9iwm9KQnxHoycL+ap_KQ AT mail DOT gmail DOT com> <CAJouXQksOsqWV=pVAJrXPn2FKtAyUO3QTxpugJ9R9rLGEN91UQ AT mail DOT gmail DOT com> <20190712153351 DOT GH3772 AT calimero DOT vinschen DOT de> <2f15106bf3becd524ac77e7bf0209d31 AT smtp-cloud9 DOT xs4all DOT net> <20190715075327 DOT GL3772 AT calimero DOT vinschen DOT de>
In-Reply-to:	<20190715075327.GL3772@calimero.vinschen.de>
User-Agent:	mua.awk 0.99

On Mon, 15 Jul 2019 09:53:27, Corinna Vinschen  wrote:

> On Jul 14 15:19, Houder wrote:

> > .. uhm, just a note in the interest of accuracy ...
> >
> >  - standard signals (which include USRSIG1 and USRSIG2) are not queued
> >    (traditional signal semantics)
> >  - only real-time signals should be queued ...
> 
> I think queing here means just what you outline above.  It's kind of a
> queue of pending signals and in Cygwin it's actually literally a queue.

> It's >>> a kind of _queue_ <<< of pending signals ...

Not a Q if it would mean that a specific signal can be inserted more than
once in this Q ...

I am fully aware that you know all about Unix/Linux, but

    for the sake of clarity:

20.12 (Signals are not queued) of LPI

    "The set of pending signals is only a "mask"; it indicates whether or
     not a signal has occurred, but NOT how many times it has occurred. In
     other words, if the same signal is generated multiple times while it
     is blocked, then it is recorded in the set of pending signals, and
     later delivered, just ONCE. (One of the differences between standard
     and realtime signals is that realtime signals are queued, as discussed
     in Section 22.8.)

     Listing 20-6 and Listing 20-7 show two programs that can be used to
     observe that signals are not queued. ... "

Meaning the queue in Cygwin is not really a Q ...

Regards,
Henri


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -