On Mon, 21 Apr 2025 21:54:03 +0200 Roland Mainz via Cygwin <cygwin@cygwin.com> wrote:
> Hi! > > ---- > > Running the git testsuite I got a hang of the > "t1004-read-tree-m-u-wf.sh" test in Cygwin 3.7 - the same test worked > AFAIK OK with Cygwin 3.5.x. > > My guess: |wait_sig()| and |_sigfe()| are involved, maybe this is a > signal issue.. > > 1. Versions: Cygwin 3.7.0-0.68.g37c49decc835.x86_64 / Windows 10 > 2. Steps to reproduce: > ---- snip ---- > mkdir gittest > cd gittest/ > git clone -b 'v2.45.1' https://github.com/git/git.git > cd git > autoconf > automake > CC="gcc -std=gnu17" ./configure > time make -j4 all > time nice make -i test > ---- snip ---- > Thanks for the report. However, I could not reproduce the issue. The cygwin version is 3.7.0-dev-68-g37c49decc835 There was two problems. 1. automake error $ automake configure.ac: error: no proper invocation of AM_INIT_AUTOMAKE was found. configure.ac: You should verify that configure.ac invokes AM_INIT_AUTOMAKE, configure.ac: that aclocal.m4 is present in the top-level directory, configure.ac: and that aclocal.m4 was recently regenerated (using aclocal) automake-1.17: error: no 'Makefile.am' found for any configure output 2. testsuite runs without hang. $ cat t1004-read-tree-m-u-wf.counts total 17 success 16 fixed 0 broken 0 failed 0 missing_prereq ,SANITY > Process "git merge-recursive branch-point -- side-b side-a" launched > by "/bin/sh t1004-read-tree-m-u-wf.sh" hangs forever with this stack > trace: > ---- snip ---- > Thread 3 (Thread 8148.0x1238 "commune"): > #0 0x00007ffe68f8d574 in ntdll!ZwWaitForSingleObject () from > /cygdrive/c/Windows/SYSTEM32/ntdll.dll > #1 0x00007ffe66b4920e in WaitForSingleObjectEx () from > /cygdrive/c/Windows/System32/KERNELBASE.dll > #2 0x00007ffe333c5a82 in cygthread::stub > (arg=arg@entry=0x7ffe335b6618 <threads+88>) at > /usr/src/debug/cygwin-3.7.0-0.68.g37c49decc835/winsup/cygwin/cygthread.cc:194 > #3 0x00007ffe333c6555 in _cygtls::call2 (this=0x5fce00, > func=0x7ffe333c59de <cygthread::stub(void*)>, arg=0x7ffe335b6618 > <threads+88>, buf=buf@entry=0x5fcd20) at > /usr/src/debug/cygwin-3.7.0-0.68.g37c49decc835/winsup/cygwin/cygtls.cc:41 > #4 0x00007ffe333c660a in _cygtls::call (func=<optimized out>, > arg=<optimized out>) at > /usr/src/debug/cygwin-3.7.0-0.68.g37c49decc835/winsup/cygwin/cygtls.cc:28 > #5 0x00007ffe66f17374 in KERNEL32!BaseThreadInitThunk () from > /cygdrive/c/Windows/System32/KERNEL32.DLL > #6 0x00007ffe68f3cc91 in ntdll!RtlUserThreadStart () from > /cygdrive/c/Windows/SYSTEM32/ntdll.dll > #7 0x0000000000000000 in ?? () This does not seem to be a signal problem but be a thread creation problem. I have no idea why and when this happens. -- Takashi Yano <takashi.y...@nifty.ne.jp> -- 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
