X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C4E8B3849AC5 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1715850892; bh=5gBSVQDzO61SZa1xc0WQYuQ1n60ySZTU5bAMxSTSNPM=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=QU7vSAXdJAqyDod22wbZ89enULHK560QR7+WGOcJGH1ykcZlAmYa5czMyRp0bR2Ii avFB3J40XMWG1GURkoxxTzWo2zhmh/AALhL5oolpIkNu06sX+aC2lfiqY1yX2s5odM Nq1R0qO2saYV4H41NSO+G0l7dmG/jeSG9/X5jKQo= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 01464384A880 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 01464384A880 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1715850865; cv=none; b=phVLabs684SRtsz2bIQsuMHAYbSNt5VuP6H93/461ctkKaGiMqJ8tAe6JxK/ysp+TnXN5shnAi54s1Gv5V7fld+eZjAGavF4uXymbTR8ze79sP8DNPMhyeKemCF+eZBkMxfZ3gvKH2XDwPOrRo0syjjC6kbcvaIOTiXZSOhodXI= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1715850865; c=relaxed/simple; bh=3SSmrs3vaGqfPl2ZR8F5JWlAOPQxIlPD5VHfL5OtvXI=; h=Date:From:To:Subject:Message-Id:Mime-Version:DKIM-Signature; b=BbA2Bq2Xmr1/k/7X1xFoNWMWFXbUDI0aWe6BwrOKfNjLi2TqYWXu64XykDwk+fuTevdft3Fdn+dzS3LI4hKdqwDKxW8oYwE5WbHGEipIN6ubFllxD1R3f4QGtTbtMb7MuFwd/D4FmUsxJWi+6PPeLaJ8kKtTZ31AefMCdtHFeP4= ARC-Authentication-Results: i=1; server2.sourceware.org Date: Thu, 16 May 2024 18:14:18 +0900 To: cygwin AT cygwin DOT com Subject: Re: cygwin application hangs on closing console Message-Id: <20240516181418.c97d8fb42b34efd903f81b01@nifty.ne.jp> In-Reply-To: References: <20240423035104 DOT 85352f8a8d821c0f4d569d18 AT nifty DOT ne DOT jp> <20240423192606 DOT 7b4aa04685afca2525eb5ed3 AT nifty DOT ne DOT jp> <6dd8a568-88c0-42d5-aa46-b09247cdecec AT johannesthoma DOT com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 X-Spam-Status: No, score=-5.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, SPF_HELO_PASS, SPF_PASS, TXREP, WEIRD_PORT autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org 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: Takashi Yano via Cygwin Reply-To: Takashi Yano Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Wed, 15 May 2024 17:48:49 +0200 Johannes Khoshnazar-Thoma wrote: > Hi again, > > Am 15.05.24 um 17:37 schrieb Johannes Khoshnazar-Thoma: > > Hi again, > > > > Am 23.04.24 um 12:26 schrieb Takashi Yano: > >>>> Thanks for the report. Could you please test cygwin1.dll 3.5.3-1 > >>>> wihch is the latest cygwin release? > >>>> > > > > We retried the tests with cygwin1.dll 3.5.3-1 and it looks like > > the issue is still there. Here's an excerpt from the gdb debug > > session: > > > Sorry somehow the formatting got messed up I try again: Thanks for testing and the additional information. > (gdb) info thread > Id Target Id Frame > * 1 Thread 0x11cc 0x00007ffe579d5ea4 in ntdll!ZwWaitForSingleObject () from C:\src\dlls-syms\ntdll.dll\6502806A1cf000\ntdll.dll > 2 Thread 0x8ec 0x00007ffe579d5ee4 in ntdll!ZwReadFile () from C:\src\dlls-syms\ntdll.dll\6502806A1cf000\ntdll.dll > 3 Thread 0x55c 0x00007ffe579d5ea4 in ntdll!ZwWaitForSingleObject () from C:\src\dlls-syms\ntdll.dll\6502806A1cf000\ntdll.dll > 4 Thread 0x131c 0x00007ffe579d95f4 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\src\dlls-syms\ntdll.dll\6502806A1cf000\ntdll.dll > 5 Thread 0x9b8 0x00007ffe579d95f4 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\src\dlls-syms\ntdll.dll\6502806A1cf000\ntdll.dll > (gdb) thread 1 > [Switching to thread 1 (Thread 0x11cc)] > #0 0x00007ffe579d5ea4 in ntdll!ZwWaitForSingleObject () from C:\src\dlls-syms\ntdll.dll\6502806A1cf000\ntdll.dll > (gdb) bt > #0 0x00007ffe579d5ea4 in ntdll!ZwWaitForSingleObject () from C:\src\dlls-syms\ntdll.dll\6502806A1cf000\ntdll.dll > #1 0x00007ffe54156d1f in WaitForSingleObjectEx () from C:\src\dlls-syms\KERNELBASE.dll\660F5EEC21e000\KERNELBASE.dll > #2 0x00007ffe4a2033a0 in fhandler_console::close (this=0x800009030) at /usr/src/debug/cygwin-3.5.3-1/winsup/cygwin/fhandler/console.cc:1914 Line 1914 of fhandler/console.cc is: WaitForSingleObject (thread_sync_event, INFINITE); This waits termination of cons_master_thread(). However, it does not seem that the cons_master_thread exists in thread list obove. If the thread was terminated normally, thread_sync_event should has been set. > #0 0x00007ffe579d5ea4 in ntdll!ZwWaitForSingleObject () from C:\src\dlls-syms\ntdll.dll\6502806A1cf000\ntdll.dll > (gdb) up > #1 0x00007ffe54156d1f in WaitForSingleObjectEx () from C:\src\dlls-syms\KERNELBASE.dll\660F5EEC21e000\KERNELBASE.dll > (gdb) > #2 0x00007ffe4a2033a0 in fhandler_console::close (this=0x800009030) at /usr/src/debug/cygwin-3.5.3-1/winsup/cygwin/fhandler/console.cc:1914 > 1914 in /usr/src/debug/cygwin-3.5.3-1/winsup/cygwin/fhandler/console.cc > (gdb) p thread_sync_event > $6 = (HANDLE) 0x1510 > (gdb) p name > $7 = "cygcons.thread_sync.0", '\000' , "r", '\000' ... > (gdb) p con.owner > No symbol "con" in current context. > (gdb) p master_thread_started > $8 = true > (gdb) p unit > $9 = 0 > (gdb) p shared_console_info > $10 = {0x1a0030000, 0x0 } > (gdb) fhandler_console::close() was called twice? Or master thread had crashed without setting thread_sync_event? -- Takashi Yano -- 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