X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=XT+
	A+Z+oSwKNmW+rrsUHjPRPQPWwmzz4UoG30dJ+D2uk7Ly1LM41ljyjjcA8dEw8l3p
	4QOIv+fJS+T8JUz176Uqqm6IGHRg2L175ektOBMYi65uBFCVLK7tF3oOuDLlwzAa
	53ZDxAOZ++0csDSiO5r6AR76xsNHbYPZ1Ayh2RVc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; s=default; bh=Fb34i0CkU
	oJVM8x1lbYS8X2pyhQ=; b=x8BvKwvFhwFYDW/5zItpOSK7ptDuv8y7xd2WWHczT
	6X8KFZTz2DGMBIPB+0VHx8uTdXB7WyqCPfVFBqxgVwqnUwDcsptZcmhe1r1PkVSB
	78vJRPLx5oeHC6C29r3PQzv0Rf+Z7oAfBVmp5gocwU8ZIZpuqeZTFnIUB1qrTIWb
	AI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
X-Spam-SWARE-Status: No, score=0.4 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_NONE,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1
To: cygwin@cygwin.com
From: jojelino <jojelino@gmail.com>
Subject: gdb hangs when it calls tcsetpgrp.
Date: Fri, 28 Jun 2013 02:30:42 +0900
Lines: 14
Message-ID: <kqhsru$s8k$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:24.0) Gecko/20100101 Thunderbird/24.0a1

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.

-- 
Regards.


--
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

