X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <5089558C.7090207@cs.utoronto.ca> Date: Thu, 25 Oct 2012 11:06:52 -0400 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Emacs crashing on C-x C-g References: <5069E625.9050803@cs.utoronto.ca> <5069EA0D.7080303@cornell.edu> <5069F83D.5060502@cs.utoronto.ca> <5087E872.4070902@cs.utoronto.ca> <50885727.4050305@cornell.edu> <50885D17.9090101@cs.utoronto.ca> <50894F58.6050000@cornell.edu> <508952E5.70200@cs.utoronto.ca> <50895454.3040406@redhat.com> In-Reply-To: <50895454.3040406@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 On 25/10/2012 11:01 AM, Eric Blake wrote: > On 10/25/2012 08:55 AM, Ryan Johnson wrote: >>>>> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12697 >>>>> >>>>> I imagine it will be fixed before the release of Emacs 24.3. >>>> Agree the initial part is emacs. But I suspect the confused bash >>>> business is not. ^G should either send SIGINT or not, this core dump >>>> thing is not cool. >>> Do you know whether this is Cygwin-specific? Have you checked to see >>> what happens on Linux? >> Oops, you're right: I see the exact same behavior on linux. However, >> that's via ssh in a mintty window, so it could still be mintty. Can >> somebody running Linux directly verify, perhaps? > Linux (at least my setup on Fedora 17) has the same problem - when using > emacs as the editor under 'git commit', an ill-timed ctrl-G on my part > unceremoniously kills emacs as a result of sending the SIGINT to the > entire process group. I hate the behavior, but it is definitely not > cygwin-specific. Right, but what happens to processes when you hit ^G after resetting the terminal to use ^C? Does it cause a seg fault? That's the part that might still be cygwin-specific. And yes, hopefully emacs fixes this Real Soon Now... Ryan -- 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