X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 16 Jun 2009 17:39:23 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: job control "Bad address" error Message-ID: <20090616153923.GA30240@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <7vd494i72q DOT fsf AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Jun 16 15:28, Eric Blake wrote: > Haojun Bao gmail.com> writes: > > > type the command: > > cat|cat > > > > type ^Z, type > > bg > > I can also reproduce it under cygwin 1.7, and further clarified that it is the > second cat that is failing: > > $ sleep 100 | cat > ^Z > $ bg > cat: -: Bad address > > I'm not quite sure how to strace this, since you can't use ^Z to suspend an > active strace. But my guess is that there is a bug in cygwin1.dll pipe > handling code, such that it dereferences bad memory when resuming execution of > a read from a pipe after a SIGSTOP; cat is just reporting the EFAULT from a > failed read() call. I have a patch for this in the loop. Actually it is supposed to fix the "Bad address" problem in git(*), but the underlying problem is apparently the same. Corinna (*) http://cygwin.com/ml/cygwin/2009-06/msg00546.html -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/