X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=wVGSLWhpu4HR1cKd GCDCJhMokCZyA6WMMHiYJLX+m/8x63LgVVTBSEhYnHqkGODEHnWFnpw730MJGPoK kAfVVwnyxAHCuH0ICtmIMI+ePd+kGtsE/t0/xK0rMrIhdNCyrUcccEI+ld7xbV+U vESIwqGjT5pqW7XPnwm4jWsble0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=default; bh=0OHiTZTSoswMGdMfMVDfK2 ggvlc=; b=kbSkMaqKSdzT+7TpK74YqbEUciUpZ8Qzlak5gLS9No+nr19224nATp ajv0rhpiZp7GbrKVZi7IxO/4uXmsQWfr8/QsNeEUWx9Q2eEWb4Utn1cCVTjHGFUx uh3jBN2a61a6W6jbjB2XgXQPPAWID5p3IMAX9hCg7+lAKDpG4bn2U= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-4.2 required=5.0 tests=AWL,BAYES_20,KHOP_RCVD_UNTRUST,KHOP_THREADED,NO_DNS_FOR_FROM,RCVD_IN_DNSWL_MED,TW_YG autolearn=ham version=3.3.1 Message-ID: <51B05080.3030106@noprivatereply.com> Date: Thu, 06 Jun 2013 11:04:00 +0200 From: "Seb.Th" Reply-To: cygwin_ml AT noprivatereply DOT com User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: resuming backgrounded job causes hang (Cygwin 1.7.19 / Dothan 1.7GHz) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Le 06/06/2013 08:25, Sumudu Fernando a écrit : > I'm having a weird issue in 1.7.19. As per the subject line, when I > try to resume a backgrounded job, I get a hang (after bash echoes the > job name). I couldn't find anything about this in the list archives, > possibly because it may be limited to specific architectures (more > below). > > simple testcase from a fresh terminal (I'm using the default mintty, with bash) > $ ls | less > > $ fg > > whereupon bash echoes the job name (in my case "ls -hF --color=tty | > less -r") and then nothing happens (no response to input AFAICT) > > Interesting things: > - this only happens on my (ancient) laptop (this is why I mentioned > the processor in the subject line) -- it *does not* happen on my > desktop machine (which is a Q6600, nearly ancient now I suppose). > - Windows task manager shows the process I tried to resume at high CPU > usage, and if I kill it from there ("end process") bash recovers fine > - I can open a separate cygwin terminal and see the "ls" in the output > of ps. It does *not* have an "S" beside it to indicate a suspended > process. "kill" does nothing, "kill -9" hangs (until I kill via task > manager). > > I attached cygcheck output; I did get some errors (that are in the > file also) but I don't know what they actually mean (if anything). > > FWIW, this did not happen with 1.7.17 (I skipped 1.7.18). This problem seems to be very similar to the thread "Bash sub-shell freezing in Midnight Commander". Something went wrong after 1.7.17 (or its dependencies ?) -- 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