From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11018 invoked by alias); 27 Jun 2013 17:46:08 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 10961 invoked by uid 89); 27 Jun 2013 17:46:08 -0000 X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1 Received: from mho-03-ewr.mailhop.org (HELO mho-01-ewr.mailhop.org) (204.13.248.66) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 27 Jun 2013 17:46:06 +0000 Received: from pool-72-74-71-174.bstnma.fios.verizon.net ([72.74.71.174] helo=cgf.cx) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1UsGGj-000Ivf-6h for cygwin@cygwin.com; Thu, 27 Jun 2013 17:46:05 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 2BDFC60143 for ; Thu, 27 Jun 2013 13:46:04 -0400 (EDT) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19xOFYLuDD59VFjkZdy1v0p Date: Thu, 27 Jun 2013 17:52:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: gdb hangs when it calls tcsetpgrp. Message-ID: <20130627174604.GC7709@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2013-06/txt/msg00688.txt.bz2 On Fri, Jun 28, 2013 at 02:30:42AM +0900, jojelino wrote: >I was using gdb for debugging ffmpeg raising SIGFPE. but gdb hangs after >entering command among of s,n,si,ni. >gdb has same pgrp over pgrp of debuggee. when tcsetpgrp is called in >gdb, you already know it sends __SIGSETPGRP signal to suspended >debuggee. but the debugger already suspended all thread of debuggee >without distinguishing whether the victim thread is wait_sig or not. so >the suspend process doesn't wake up until debugger handles debug event. >which is the cause of hang. >Although it seems that cygwin developers have already aware of sort of >this issue according to fhandler_termios.cc:85, so, it would be good if >cygwin can defer sending signal that would block for sure. Yep. I've mentioned this issue here several times. You should use mintty for debugging. It does not have this problem. cgf -- 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