Path: ...!news.nobody.at!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Rainer Weikusat <rweikusat@talktalk.net>
Newsgroups: comp.unix.programmer
Subject: Re: signal handling issues
Date: Thu, 06 Feb 2025 22:31:47 +0000
Lines: 23
Message-ID: <87seoqemcs.fsf@doppelsaurus.mobileactivedefense.com>
References: <874j1g18x2.fsf@doppelsaurus.mobileactivedefense.com>
	<tBPmP.1043754$2xE6.1002585@fx18.iad>
	<1l577l-gvh.ln1@ID-313840.user.individual.net>
	<e6ue7l-9uh.ln1@ID-313840.user.individual.net>
Mime-Version: 1.0
Content-Type: text/plain
X-Trace: individual.net ir63d6/V0JXehdPd59m6ogIot7yiiFV+ieVh223I2XiWJVq/0=
Cancel-Lock: sha1:Axkk6eYiJ+croUewFS3XHVj1dEM= sha1:ejWXHdIvhofNUSIWxBc/SbWe3mY= sha256:rty9YnJ9pBk91UnLTwDyHyBYipEEKD8dnnxYPoCxGJM=
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Bytes: 1812

Geoff Clare <geoff@clare.See-My-Signature.invalid> writes:
> Geoff Clare wrote:
>
>> After some digging I found the source of the change,
>> which was this bug:
>> 
>> https://austingroupbugs.net/view.php?id=66
>> 
>> It updated some text on the signal() page and then copied it into
>> XSH 2.4.3.
>> 
>> So the conflict Rainer has identified was already there in Issue 6,
>> but only for signal handlers installed using signal(), not sigaction().
>> Obviously it made no sense for there to be different signal handler
>> rules depending on which function installed the handler, hence the
>> copying.
>
> I have now reported the problem to the Austin Group. See
> https://austingroupbugs.net/view.php?id=1905

Thanks. I was thinking on-and-off if I should do this myself but I would
certainly have made a much worse job of it due to being entirely
unfamiliar with the processes involved here.