Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 26 Jan 2004 17:50:46 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Add "Why doesn't ^Z (Suspend) work?" to FAQ? Message-ID: <20040126225046.GA31873@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <20040126204659 DOT GB7202 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com On Mon, Jan 26, 2004 at 03:07:55PM -0600, Brian Ford wrote: >ford AT fordpc ~ >$ sleep 100 > >[^Z here] >[1]+ Stopped sleep 100 > >ford AT fordpc ~ >$ fg >sleep 100 >Segmentation fault (core dumped) Should be fixed in CVS. I'm amazed that the test suite didn't catch this and/or it isn't biting more people. It was a simple case of nested signal handlers not working and I tested that heavily early in my signal rewrite. Oh well. Like most of the problems here in the last two weeks, this just goes to show the need for beefing up cygwin's test suite. cgf -- 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/