X-Recipient: archive-cygwin AT delorie DOT 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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=vMOhYznXRimHv/ftno097HRTrnSFlZSQaTIs1dtE9AU
	TWXjQi5b/odgdmTdQ2upne0ujlSE5VVX7hSzGzsRRcITGMsRxrWaqR5efqL6JOlw
	Tg0tVka2B9Up4KsbKH4XxcdwQYxxKSuq0BgNYqyw9WdHCdzJlJyHw8lMIwjT5l1Y
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=kEkPR70VvD07WL/H+Mm4g3YbTqU=; b=iEerSGH8okGjY2edD
	xn2yohJINgXintF4/BKNP84+iplMzL+pQo3QZq7Lrpfue2MVUg8zjRDttvQcAlD3
	B2q4KNN8SemSADYef3WlNLBRCg0HIWkS9MoeimJChjkTH17Y4/Inp+7gaafps9rv
	J5SRoKRzWfi2Tm9TxYxSFlt4NI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RP_MATCHES_RCVD,SPF_NEUTRAL autolearn=ham version=3.3.1
Message-ID: <516C3D0D.6080508@cs.utoronto.ca>
Date: Mon, 15 Apr 2013 13:46:53 -0400
From: Ryan Johnson <ryan DOT johnson AT cs DOT utoronto DOT ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Debugging totally broken with latest everything?
References: <516C24C5 DOT 80107 AT gmail DOT com> <20130415171412 DOT GA3356 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20130415171412.GA3356@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 15/04/2013 1:14 PM, Christopher Faylor wrote:
> On Mon, Apr 15, 2013 at 05:03:17PM +0100, Dave Korn wrote:
>>   Some notes on the above:
>>
>>   The same happens with both the previous version and current snapshot of the
>> cygwin dll.  It also happens with both current gdb and an old gdb
>> 6.8.0.20080328-cvs that I have lying around.
>>
>>   The hw.exe in question is your bog-standard hello world, compiled with "-g
>> -O0" using gcc4-4.5.3-3.
>>
>>   "kill -9" won't kill gdb; I have to use Windows task manager.  If I've
>> attached gdb to the hung gdb, I can kill it from there using the "k" instruction.
>>
>>   Anyone else having similar problems?
> You're probably seeing a known bug in gdb where it no longer works well
> when run from a console window.  There is a race where gdb tries to get
> tty information from a stopped cygwin process.  Although I didn't
> introduce the problem, I have tried to fix it from time to time without
> much luck.
I've also seen the problem, my workaround so far has been to ensure the 
process is running again before attaching gdb to it (assuming you 
stopped it with ^Z so that jobs -p could report its pid). Not that I 
actually remember to do this most of the time...

> Debugging from mintty will probably work better.
That's a rather unfortunate interaction with the long-standing "feature" 
that interrupting programs with ^C only works if gdb runs in a console 
window (STC I used today is below in case I've gotten something wrong).

Am I missing some obvious workaround?

Ryan

STC: when compiling and running this:

#include <unistd.h>
#include <stdio.h>
int main() {
     printf("pid: %d\n", getpid());
     sleep(10);
}

... ^C does not break in (it exits normally) when gdb runs inside 
mintty; putting in a cmd.exe window allows ^C to break in with SIGTRAP 
(though the stack trace is utterly useless since the thread is in 
windows land at that point).



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