I'm using bash as installed by Git for Windows (MSys2 bash). It has been working fine for some time, but now it is hanging forever when I try to start it. The bash window will open up, but nothing happens and a prompt does not show. I am able to press Ctrl-C and have a prompt show up and execute commands. Trying to run
bash again from within the shell is slow again, though.
I haven't customized any startup scripts.
I tried running
strace bash -li >& ~/log.txt. I don't really know what it all means, but the first exception I see is:
58 460060 [main] bash 7644 sigaction_worker: signal 20, newact 0xFFFFC100 (handler 0x100428CE0), oa 0xFFFFBFB0 44 460104 [main] bash 7644 sigaction: 0 = sigaction(20, 0xFFFFC100, 0xFFFFC120) 43 460147 [main] bash 7644 close: close(4) --- Process 8236, exception c00000fd at 000007fefba52948 56 460203 [main] bash 7644 fhandler_base::close: closing 'pipe:' handle 0x910 61 460264 [main] bash 7644 close: 0 = close(4) 52 460316 [main] bash 7644 read: read(3, 0xFFFFC1C0, 128) blocking
A while later it gets into a repetitive loop and continues this forever:
--- Process 5604, exception c0000005 at 000007fefba52948 62 9031 [main] bash 5604 exception::handle: In cygwin_except_handler exception 0xC0000005 at 0x7FEFBA52948 sp 0xFFFFB418 33 9064 [main] bash 5604 exception::handle: In cygwin_except_handler signal 11 at 0x7FEFBA52948 45 9109 [main] bash 5604 _cygtls::inside_kernel: pc 0x7FEFBA52948, h 0x7FEFB850000, inside_kernel 1 39 9148 [main] bash 5604 seterrno_from_nt_status: /usr/src/MSYS2-packages/msys2-runtime/src/msys2-runtime/winsup/cygwin/fhandler_mailslot.cc:132 status 0xC0000034 -> windows error 2 33 9181 [main] bash 5604 geterrno_from_win_error: windows error 2 == errno 2 35 9216 [main] bash 5604 sig_send: sendsig 0x5C4, pid 5604, signal 11, its_me 1 42 9258 [main] bash 5604 sig_send: wakeup 0x604 33 9291 [main] bash 5604 sig_send: Waiting for pack.wakeup 0x604 37 9328 [sig] bash 5604 sigpacket::process: returning -1 39 9367 [sig] bash 5604 wait_sig: signalling pack.wakeup 0x604 52 9419 [main] bash 5604 sig_send: returning 0x0 from sending signal 11 --- Process 5604, exception c0000005 at 000007fefba52948 66 9485 [main] bash 5604 exception::handle: In cygwin_except_handler exception 0xC0000005 at 0x7FEFBA52948 sp 0xFFFFB418 33 9518 [main] bash 5604 exception::handle: In cygwin_except_handler signal 11 at 0x7FEFBA52948 37 9555 [main] bash 5604 _cygtls::inside_kernel: pc 0x7FEFBA52948, h 0x7FEFB850000, inside_kernel 1 ... (repeats forever) ...
I gather that the first exception I saw (c00000fd) is a stack overflow, and the repeating one (c0000005) is an access violation.
The most recently loaded DLLs before the first exception are
C:\Program Files\DGAgent\plugins\8E4EA70A-6128-4B57-BD3F-8E9E0F0DA6BB\COM_Sensor64.dll C:\Windows\System32\privman64.dll
The DGAgent one is from some software called Digital Guardian that my employer has installed to monitor our computers. I wouldn't be surprised if that is the culprit, but I don't know how to be sure.
I've tried restarting the computer. Any ideas about next steps for debugging? My end goal is to have bash working so I can run gitlab-runner on this Windows machine again.