From: Jeremy Drake <cygwin@jdrake.com>
To: cygwin@cygwin.com
Subject: frequent hangs running ldd
Date: Fri, 24 May 2024 11:50:35 -0700 (PDT) [thread overview]
Message-ID: <fd3b2d14-0d16-9e66-f7ea-daadc0c5bfcc@jdrake.com> (raw)
Seen on msys2, but doesn't seem specific to it.
Frequently, when running ldd in a loop, it will hang. I managed to get a
backtrace from gdb with symbols:
(gdb) bt
#0 0x00007ffecea0fa34 in ntdll!ZwDeviceIoControlFile ()
from /c/Windows/SYSTEM32/ntdll.dll
#1 0x00007ffecbead7a9 in KERNELBASE!GetConsoleScreenBufferInfoEx ()
from /c/Windows/System32/KERNELBASE.dll
#2 0x00007ffecbef58dc in KERNELBASE!GetConsoleTitleW ()
from /c/Windows/System32/KERNELBASE.dll
#3 0x00007ffecbfb8195 in KERNELBASE!GetConsoleProcessList ()
from /c/Windows/System32/KERNELBASE.dll
#4 0x000000018015851f in fhandler_pty_common::get_console_process_id (
pid=19348, match=match@entry=true, cygwin=cygwin@entry=false,
stub_only=stub_only@entry=false, nat=nat@entry=false)
at /C/_/msys2-runtime/src/msys2-runtime/winsup/cygwin/fhandler/pty.cc:95
#5 0x0000000180101e3b in fhandler_console::attach_console (
owner=<optimized out>, err=err@entry=0x0)
at /C/_/msys2-runtime/src/msys2-runtime/winsup/cygwin/fhandler/console.cc:76
#6 0x0000000180102d40 in fhandler_console::set_output_mode (m=tty::native,
t=0x1a0030028, p=0x800021d68)
at /C/_/msys2-runtime/src/msys2-runtime/winsup/cygwin/fhandler/console.cc:853
#7 0x000000018010d6cc in fhandler_console::set_console_mode_to_native ()
at /C/_/msys2-runtime/src/msys2-runtime/winsup/cygwin/fhandler/console.cc:4189
#8 0x000000018010d71d in ContinueDebugEvent_Hooked (p=26628, t=26656, s=65538)
at /C/_/msys2-runtime/src/msys2-runtime/winsup/cygwin/fhandler/console.cc:4238
#9 0x0000000100401bd7 in ?? ()
#10 0x000000010040279f in ?? ()
#11 0x00000001800483a7 in dll_crt0_1 ()
at /C/_/msys2-runtime/src/msys2-runtime/winsup/cygwin/dcrt0.cc:1015
#12 0x0000000180045f63 in _cygtls::call2 (this=0x7ffffce00,
func=0x180047240 <dll_crt0_1(void*)>, arg=0x0,
buf=buf@entry=0x7ffffcdf0)
at /C/_/msys2-runtime/src/msys2-runtime/winsup/cygwin/cygtls.cc:41
#13 0x0000000180046014 in _cygtls::call (func=<optimized out>,
arg=<optimized out>)
at /C/_/msys2-runtime/src/msys2-runtime/winsup/cygwin/cygtls.cc:28
#14 0x0000000000000000 in ?? ()
Other attempts without symbols showed the same Windows APIs at least.
next reply other threads:[~2024-05-24 18:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 18:50 Jeremy Drake [this message]
2024-05-24 19:54 ` Takashi Yano
2024-05-24 20:09 ` Takashi Yano
2024-05-24 21:46 ` Jeremy Drake
2024-05-24 22:17 ` Takashi Yano
2024-05-24 22:24 ` Mark Geisert
2024-05-24 22:26 ` Jeremy Drake
2024-05-24 22:38 ` Jeremy Drake
2024-05-24 23:29 ` Jeremy Drake
2024-05-25 2:28 ` Jeremy Drake
2024-05-25 2:29 ` Jeremy Drake
2024-05-28 1:58 ` Takashi Yano
2024-05-28 2:16 ` Takashi Yano
2024-05-24 22:43 ` Mark Geisert
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=fd3b2d14-0d16-9e66-f7ea-daadc0c5bfcc@jdrake.com \
--to=cygwin@jdrake.com \
--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).