X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_33,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Eric Blake Subject: Re: job control "Bad address" error Date: Tue, 16 Jun 2009 15:28:14 +0000 (UTC) Lines: 26 Message-ID: References: <7vd494i72q DOT fsf AT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes 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 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. -- Eric Blake volunteer cygwin coreutils maintainer -- 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/