From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: guile: guild compile hangs
Date: Wed, 28 Jun 2017 19:19:00 -0000 [thread overview]
Message-ID: <9a0f7b2b-3516-fd56-2285-51125e88679e@t-online.de> (raw)
In-Reply-To: <cfd66c44-9740-4008-7d27-5c848a4e71da@gmail.com>
Am 28.06.2017 um 13:58 schrieb Marco Atzeri:
> On 28/06/2017 01:32, Hans-Bernhard Bröker wrote:
>> FWIW, it also hangs when trying to build gdb from GIT sources (in the
>> gdb/data-directory folder).
>> I see it with "current" of Cygwin, i.e. 2.0. The last time it worked
>> was May 20th, apparently. The first big install after that date, here,
>> was the big round of Python updae on May 27th.
> potential candidates are:
> - libgmp
> - libiconv
> - libintl
> - libltdl
> - libunistring
> - libgc
> and cygwin itself
The closest of these in terms of update time relative to the date this
started to fail for me would be libgc-7.6.0-1 update I installed on May
12th. gdb-ing into the stuck guile process shows about multiple threads
in a waiting state:
(gdb) info thr
Id Target Id Frame
7 Thread 17376.0x4188 0x00007ffd1add8d71 in ntdll!DbgBreakPoint ()
from /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll
6 Thread 17376.0x2bc0 0x00007ffd1add5f04 in
ntdll!ZwWaitForMultipleObjects () from
/cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll
* 5 Thread 17376.0x356c 0x00007ffd1add5f04 in
ntdll!ZwWaitForMultipleObjects () from
/cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll
4 Thread 17376.0x1754 0x00007ffd1add5f04 in
ntdll!ZwWaitForMultipleObjects () from
/cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll
3 Thread 17376.0x868 0x00007ffd1add5f04 in
ntdll!ZwWaitForMultipleObjects () from
/cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll
2 Thread 17376.0x2f3c 0x00007ffd1add5474 in ntdll!ZwReadFile ()
from /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll
1 Thread 17376.0x3040 0x00007ffd1add5f04 in
ntdll!ZwWaitForMultipleObjects () from
/cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll
and several of those waits do originate in cyggc-1.dll.
--
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
next prev parent reply other threads:[~2017-06-28 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 23:04 Yaakov Selkowitz
2017-06-25 21:22 ` Yaakov Selkowitz
2017-06-26 9:46 ` Marco Atzeri
2017-06-26 10:52 ` Marco Atzeri
2017-06-27 19:53 ` Marco Atzeri
2017-06-27 23:32 ` Hans-Bernhard Bröker
2017-06-28 11:58 ` Marco Atzeri
2017-06-28 19:19 ` Hans-Bernhard Bröker [this message]
2017-06-28 19:45 ` Marco Atzeri
2017-06-29 17:47 ` Hans-Bernhard Bröker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a0f7b2b-3516-fd56-2285-51125e88679e@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).