DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 54TFX15r610668 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 54TFX15r610668 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=lPoT4DdD X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6BB1A385843F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1748532779; bh=NbdRwy0EXXFuZlTDYXDxIL4TbQnlhtLhdObL+Vsq+sg=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=lPoT4DdDEDzYp16yrM2YRrkXziQ/mxWY7VbfUZExz4uuaQPajI9UtD+Tib/vOK9+U qggsoJxyyxzaqgq8LQp0kNO21elk1u40oNINr05CQ0HVyvkSMa7+anoJF/fvUnDhbs nwnIpi57Deb6Og+lHbWbxWFW6jRGqyHkCKkWoIIE= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 88CDD3857B9B ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 88CDD3857B9B ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1748532745; cv=none; b=IT/uXeRbgxa/A3A+ZpUxVOMyUA2EMYOPlZF5+unfTxUQSHgNk42OfahCM/L2LsD9ed5kVMOaoMWDp4NX8ddv7rVycsdFX1aU8mrdBhUkw7VMoBx5vHkzhrqlqBv4LlCI+Di87U9pTToKXMIyZDOCQnUrpxdlvmBQ/goI9QjnC3E= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1748532745; c=relaxed/simple; bh=il8bkiNr939b3XKqQmLj3nDmW4MlaqbjXGBf56tdVLg=; h=Subject:To:From:Message-ID:Date:MIME-Version; b=D6IbEQfdrRYngjpXXnmaDGWMqG6lwaro4nJd5q4mtxjjfa/A6PU9dw8obkVqnI+ibUTQ+ojDJEJHh57Bu1z4Q3ShNIrJPkYgbygDlHOONyAr+PVhBF+rY/GtKOgo2AqFctwsnYUt1O6ChdEFDXMmeWtPmBWXURb/kQig8oMUre4= ARC-Authentication-Results: i=1; server2.sourceware.org Subject: Re: Crash or hang if SIGSEGV+SIGALRM are nested To: cygwin AT cygwin DOT com References: <20250528215707 DOT ddb72fb28122c3ed07da8c5b AT nifty DOT ne DOT jp> <20250529102846 DOT 8144f502c3f17decbe6700c1 AT nifty DOT ne DOT jp> Message-ID: <76940263-49e8-1b4a-17f2-11f5545014ab@t-online.de> Date: Thu, 29 May 2025 17:32:19 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 SeaMonkey/2.53.20 MIME-Version: 1.0 In-Reply-To: <20250529102846.8144f502c3f17decbe6700c1@nifty.ne.jp> X-TOI-EXPURGATEID: 150726::1748532740-3D7F9986-0EB77EB6/0/0 CLEAN NORMAL X-TOI-MSGID: 0c837718-ae1e-48f0-8673-b116d177eeea X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Christian Franke via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Christian Franke Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 54TFX15r610668 Takashi Yano via Cygwin wrote: > On Wed, 28 May 2025 21:57:07 +0900 > Takashi Yano wrote: >> Hi Christian, >> >> On Mon, 19 May 2025 12:55:46 +0200 >> Christian Franke wrote: >>> The attached testcase was originally intended to investigate why a >>> SIGSEGV from non-signal code could interrupt an already running signal >>> handler. >>> https://sourceware.org/pipermail/cygwin-patches/2025q2/013703.html >>> >>> If run without strace, the testcase may crash silently (with exit status 0): >>> >>> $ uname -r >>> 3.7.0-0.98.gb39b510c1ce6.x86_64 >>> >>> $ gcc -o sigsegvalrm sigsegvalrm.c >>> >>> $ while { ./sigsegvalrm; s=$?; echo exit $s; test $s = 42; }; do :; done >>> ... >>> [SEGV during ALRM] >>> [SEGV] >>> [ALRM during SEGV] >>> [ALRM] >>> 101 total, 24 ALRM during SEGV, 13 SEGV during ALRM >>> exit 42 >>> ... >>> [SEGV during ALRM] >>> [ALRM] >>> [SEGV] >>> [ALRM] >>> [SEGV] >>> [ALRM during SEGV] >>> [SEGV] >>> [ALRM] >>> [SEGV] >>> exit 0 >>> >>> >>> If the above was run with 'strace ./sigsegvalrm', the result was an >>> infinte loop: >>> https://cygwin.com/pipermail/cygwin/2025-May/258144.html >>> >>> Fortunately this is fixed since b39b510c. A new result: >>> >>> ... >>> [SEGV during ALRM] >>>   205  556472 [main] sigsegvalrm 1342 fhandler_console::write: 19 = >>> fhandler_console::write(...) >>>    91  556563 [main] sigsegvalrm 1342 write: 19 = write(1, 0x100403020, 19) >>>    81  556644 [main] sigsegvalrm 1342 clock_nanosleep: clock_nanosleep >>> (0.001000000) >>>  8396  565040 [itimer] sigsegvalrm 1342 timer_tracker::thread_func: >>> 0x7FFE4CC69640 timer expired >>>   230  565270 [main] sigsegvalrm 1342 clock_nanosleep: 0 = >>> clock_nanosleep(1, 0, 0.001000000, 0.d) >>>   123  565393 [itimer] sigsegvalrm 1342 timer_tracker::thread_func: >>> 0x7FFE4CC69640 sending signal 14 >>>   230  565623 [main] sigsegvalrm 1342 set_signal_mask: setmask 2400, >>> newmask 0, mask_bits 2400 >>>   147  565770 [main] sigsegvalrm 1342 pthread_sigmask: 0 = >>> pthread_sigmask(0, 0x100407128, 0x0) >>>   220  565990 [itimer] sigsegvalrm 1342 sig_send: sendsig 0x158, pid >>> 1342, signal 14, its_me 1 >>>   278  566268 [main] sigsegvalrm 1342 pthread_sigmask: 0 = >>> pthread_sigmask(0, 0x0, 0x100407128) >>> --- Process 148 (pid: 1342), exception c0000005 at 0000000100401287 >>>  1579  567847 [sig] sigsegvalrm 1342 sigpacket::process: signal 14 >>> processing >>>   189  568036 [sig] sigsegvalrm 1342 init_cygheap::find_tls: sig 14 >>>   235  568271 [sig] sigsegvalrm 1342 sigpacket::process: using tls >>> 0x7FFFFCE00 >>>   195  568466 [main] sigsegvalrm 1342 exception::handle: In >>> cygwin_except_handler exception 0xC0000005 at 0x100401287 sp 0x7FFFFCBE0 >>>   131  568597 [sig] sigsegvalrm 1342 sigpacket::process: signal 14, >>> signal handler 0x100401080 >>>    82  568679 [main] sigsegvalrm 1342 exception::handle: In >>> cygwin_except_handler signal 11 at 0x100401287 >>>    79  568758 [sig] sigsegvalrm 1342 sigpacket::setup_handler: >>> suspending thread, tls 0x7FFFFCE00, _main_tls 0x7FFFFCE00 >>> [~30s delay] >>> --- Process 148 (pid: 1342) thread 14964 created >>> --- Process 148 (pid: 1342) thread 14048 created >>> [~30s delay] >>> --- Process 148 (pid: 1342) thread 5184 exited with status 0x0 >>> --- Process 148 (pid: 1342) thread 5056 exited with status 0x0 >>> [several minutes delay] >>> --- Process 148 (pid: 1342) thread 9388 created >>> >>> The process then ignores SIGKILL. >> Thanks for reporting this. I finally found the solution. >> Please test >> https://cygwin.com/pipermail/cygwin-patches/2025q2/013731.html >> https://cygwin.com/pipermail/cygwin-patches/2025q2/013732.html > Updated to v2: > https://cygwin.com/pipermail/cygwin-patches/2025q2/013731.html > https://cygwin.com/pipermail/cygwin-patches/2025q2/013733.html > Problem does no longer occur if both patches are applied, thanks! I still don't fully understand why a SIGSEGV triggered by an instruction could interrupt a SIGALRM handler. https://sourceware.org/pipermail/cygwin/2025-May/258145.html I guess such behavior is valid from the POSIX point of view, but it is at least unexpected. If the SIGALRM handler is already running, it should have interrupted the thread such that the instruction triggering the segfault is not executed until the SIGALRM handler returns. -- Thanks, Christian -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple