X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sun, 2 Aug 2009 18:27:43 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Backgroud program uanble to go back
Message-ID: <20090802222743.GA8094@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <f4d6f44b0907310113u17b27472uf4f080a83d78ba48 AT mail DOT gmail DOT com>  <slrnh7bshl DOT 6sl DOT tuomov AT beer DOT modeemi DOT cs DOT tut DOT fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <slrnh7bshl.6sl.tuomov@beer.modeemi.cs.tut.fi>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Sun, Aug 02, 2009 at 08:08:21PM +0000, Tuomo Valkonen wrote:
>On 2009-07-31, Huang Bambo <bambo DOT huang AT gmail DOT com> wrote:
>>Cygwin 1.7.52 to 1.7.54 After I use Ctrl+D to make a working vim
>>background, the process will not comeback with fg command.  I havn't
>>test if other programs are the same.
>
>I can confirm that after a recent update, I get this with every single
>application I've tried: most of the time, nothing returns to the
>foreground with 'fg'.

I've just checked in what I hope is a fix for this to CVS.  There were
few details in the initial problem report so apparently I was trying to
duplicate the problem in a way that was unlike the OP.  When I tried a
different method, I was able to see a problem with 'fg'.  However,
neither you or the OP actually described the problem in enough detail
for me to know for sure if what I saw was what you saw.

>In other news the same updates have also broken X, which keeps crashing
>so often, that it's impossible to use it.  Together with this fg
>brokenness, Cygwin is ATM in pretty much completely unusable state...
>in addition to its typical dog-slowness (Cygwin rsync: 1hour for DVD to
>disk; MS robocopy: 25min...  and I don't even want to think how slow
>nanoblogger is).

You're talking about "the same updates" so it isn't clear if you are
aware of the fact that 1.7.0-56 has been released.  A few problems with
process creation were fixed there.  There have been some reports that
there are ongoing problems but I'm unable to duplicate them.

cgf

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