DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:message-id:date:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=ejv
	fC6NU8y/xiFS1f7AFjVJKCZeApk8puINL6HraJQNZRXuxSDVbV6eCAxCkyZteoly
	fY5VWBMh7fMEaZtX/gRZTvLMtrGJ7eBfPEupdByOn3Fy1YQmEnc1vSmB2/ts49RC
	n6zTJrnQ+LmHCz3G2XjHOvXBgokJLhe/yoxlqd5w=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
IronPort-SDR: Xr/f9tcBvdwwrTTNocEYVE0/ZtQIaByXHsUNmGOQ5oSj7iIm6yD1Qt/y23L4djY2iM+VLhcOJW dGW4+Qnru304jse26n/4HTmziIDcOdhW6b1G+jiYdGmqK3/2bDbvuPBn3OzKr2Zx5xuhQb8hQp uPd0SLT5HzI4mG1cft9zStVp61UrXMMQnvm1QvF92keQPB+kqruo2osrO+P1axFeCODLHioQgs hIM7i61PVxJ8I4FpTkbAmPxKxMlKXPBzzyyFTw0quOMhzJfqn54FnXYdHscX4ahEfmhc86nM86 MkY=
To: cygwin AT cygwin DOT com
From: Jan-Marek Glogowski <glogow AT fbihome DOT de>
Subject: CPU hogging by dysfunctional bash or zsh when started via mintty Cygwin terminal link
Message-ID: <7c50f8ff-3eab-f226-7963-cd43478f68b5@fbihome.de>
Date: Fri, 14 Feb 2020 03:08:54 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Hi *,

I've already been on IRC (jmux) and had a longer debug session, trying
various stuff suggested by MetaNova. This is a Cygwin64 install.

Quoting from IRC: "After a longer time (probably months), I tried to
open a cygwin terminal, which now fails. It results in an empty window
with a blinking cursor and a bash process with 100% CPU load. The box is
a Windows 10 VM and also runs an cygwin openssh server, which I normally
use for development. SSH still works fine. I also installed gdb and
tried to attach to the CPU hogging bash, but I never see a gdb prompt
just some gdb startup output."

The condensed version, of what I already did and didn't change the result:

* updated cygwin install
* gdb -p <bash hog pid> -> hangs
  - killing bash will "start" gdb with the message, that the process
already exited
* starting zsh via the mintty link results in zsh hogging the CPU.
* cygwin.bat works; same for starting bash.exe from cmd
* reinstall mintty incl. "rebase-trigger fullrebase" didn't help
* strace mintty from a cygwin.bat shell results in a SIGSEGV
  - log currently at http://paste.debian.net/1130528/
  - expires: 2020-02-17 01:57:45
* gdb mintty results in ~ the same result, then gdb -p
  - it creates some threads, a bash hog window is created with all the
other "helpers" and gdb returns with "[Inferior 1 (<pid I guess)>)
exited with normally]" to the gdb prompt
  - quitting gdb and returning to the bash prompt won't happen, until I
kill the bash window, so basically the same, then doing "gdb -p"

This all looks like a mintty problem.

What else can I do to debug / fix this problem?

Regards,

Jan-Marek

P.S. Windows installed some updates today, but since I don't know when I
opened a terminal the last time, I can't tell if that is related.

--
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