From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m0.truegem.net (m0.truegem.net [69.55.228.47]) by sourceware.org (Postfix) with ESMTPS id DDA3A3858D29 for ; Fri, 24 May 2024 22:43:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org DDA3A3858D29 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=maxrnd.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org DDA3A3858D29 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=69.55.228.47 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1716590630; cv=none; b=AoutceE8ZHYjeLqDS+jhxHjzcC/uaTzsQFx0e1sRo7uUS2nP++63FlsOq1bGh9ZKSj/WxVglncifoNdrbtfpyOM11j11ADkx8Cm2srJRVF/L3+zqczXvz8P6lZaJjySmA5UqutnbGdxL3EMQyfT2wEsiQ80mOMqcaD3su/MpGIM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1716590630; c=relaxed/simple; bh=OP9DNVUc4APtPfMCyYdtpxVspbJE3tjwCVUPItV5U/4=; h=Message-ID:Date:MIME-Version:Subject:To:From; b=CVvBI7kAz8dOXUMVbAIYh4+5bHIw/hjtM1Dgh1x0kH943dpR3Bi6k6zzAPf8ly9CccVOLUWOilhzPNpKBwjMim8wEXkiWevlqsI3zyBW4YZit2Rug6GZe4M2iTEHXzgflmB8dRkxSO+hT3OosY9yStTQwIaKfmMRCB7iX3GBDqI= ARC-Authentication-Results: i=1; server2.sourceware.org Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id 44OMn6l7007110 for ; Fri, 24 May 2024 15:49:06 -0700 (PDT) (envelope-from mark@maxrnd.com) Received: from 50-1-245-188.fiber.dynamic.sonic.net(50.1.245.188), claiming to be "[192.168.4.101]" via SMTP by m0.truegem.net, id smtpd3v9yy7; Fri May 24 15:49:01 2024 Message-ID: <1d3fed70-2f3d-48c4-b043-c06fccf7a1cc@maxrnd.com> Date: Fri, 24 May 2024 15:43:49 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: frequent hangs running ldd To: cygwin@cygwin.com References: <20240525045424.ac58c0ff5e325706b2a5f014@nifty.ne.jp> <0bd2f49b-93f6-7db4-32b6-7f3021db211e@jdrake.com> <20240525071739.167d0f2b66b3dd8d2313be19@nifty.ne.jp> <199f58b5-be55-a490-b94c-8b1ec7ff10fe@jdrake.com> Content-Language: en-US From: Mark Geisert In-Reply-To: <199f58b5-be55-a490-b94c-8b1ec7ff10fe@jdrake.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 5/24/2024 3:26 PM, Jeremy Drake via Cygwin wrote: > On Sat, 25 May 2024, Takashi Yano wrote: > >> On Fri, 24 May 2024 14:46:40 -0700 (PDT) >> Jeremy Drake wrote: >>>> Thanks for the report. However, I cannot reproduce the issue. >>>> If it always hangs in GetConsoleProcessList (), I doubt it is not a cygwin >>>> bug but a windows bug. >>>> >>>> By any chance, is the number of processes that attach to the same pty more >>>> than 32768 in your environment? >>>> >>> >>> I doubt it, I was running a shell with this command: >>> find /usr/bin -name \*.dll -printf '%p:\n' -exec ldd '{}' \; >> >> Thanks for the details. I could reproduce the issue. >> It seems that ldh.exe (which is called from ldd?) falls into infinite loop. >> However, gdb cannot attach to ldh.exe... >> > > Windbg reports that ldh.exe is already being debugged. I was able to do a > "non-invasive" attach to ldh.exe in windbg, but it doesn't seem to be able > to deal with the split debug symbols (gnulink?). I don't know if gdb can > do a non-invasive attach like that (or open a minidump assuming one could > be made from a non-invasize attach in windbg). ldd is the debugger of ldh. I found that Sysinternals Process Explorer can attach to ldh, show the threads, and can get stack backtraces which are refreshable. You have to convert addresses shown there into source-relevant addresses manually. I'm bowing out for now as I think Takashi has a handle on this. Cheers, ..mark