X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Gene Smith Subject: Re: [ANNOUNCEMENT] Updated: cygwin-1.5.25-15 Date: Tue, 23 Jun 2009 13:24:24 -0400 Lines: 30 Message-ID: References: <20080614115538.GA731@calimero.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) In-Reply-To: <20080614115538.GA731@calimero.vinschen.de> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Corinna Vinschen wrote: > On Jun 14 13:05, Corinna Vinschen wrote: >> I've uploaded a new release Cygwin 1.5.25-15. This is a bug fix >> release. >> >> >> Changes since version 1.5.25-14: >> >> - Fix a potential problem with pressing Ctrl-C in remote sessions from >> within a Windows console. Under some circumstances a Ctrl-C keypress >> in a remote session can end the remote session unexpectedly. This can >> happen, for instance, when running an ssh session with X11 forwarding. > > On second thought, this description is a bit misleading. Actually > the problem might occur in pure local circumstances as well. > > What happens is that a parent process sets the console to raw mode and > then starts a child process. When the child process starts, Cygwin > might set the console back to cooked mode without the child process > actually requesting that. When you now press Ctrl-C, instead of just > returning the ASCII value of that control code, a SIGINT signal is sent > to the parent process. > > > Corinna > I notice something like this running gdb from cygwin/rxvt. I hit c to continue the program. Then I hit ctrl-c to stop it and return to gdb prompt. Instead, this would exit gdb back the cygwin command prompt. No problem like this if running gdb from a pure cmd terminal. Same thing? -- 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