delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2013/04/15/13:14:34

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:date:from:to:subject:message-id:reply-to
:references:mime-version:content-type:in-reply-to; q=dns; s=
default; b=DG+W3jJoodsMsKsAHrqRjzYyKvleEFwaHxB5+xaOauXUSDnitTCN3
TIqoDTO92UmxIby5Hzp3Ob8mZ2xm3rvmv/oon5d0DU5RwMYF/TF2qAN2h+nGqiit
mjM6o5KmY9bWCNEw1MgPyW4d1hjWG6HB/pVVBjEsuFsSX8/LXTkWS4=
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:date:from:to:subject:message-id:reply-to
:references:mime-version:content-type:in-reply-to; s=default;
bh=/ewCpvSOunyCBmJlW/meoHgOvR0=; b=IDXaSzXxRbdBVQBUrYTeCyr1RyBN
0d0VMfmOSnbH/HLu+hPuUQoMWuNhn7Lm7vzlaVfAsiU3SFMes3GrDLVa6JVqyCoY
eefGcG7xqGr7sFVNb1WHkuwaaDvSeJD4oNXRq5yhgRovsxXJySbh14M0PMg60Q7y
u/DpnjHxpJp39Oo=
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=0.1 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/Wc18njOAmWq2ZAAYMALn0
Date: Mon, 15 Apr 2013 13:14:12 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Debugging totally broken with latest everything?
Message-ID: <20130415171412.GA3356@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <516C24C5 DOT 80107 AT gmail DOT com>
MIME-Version: 1.0
In-Reply-To: <516C24C5.80107@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

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.

Debugging from mintty will probably work better.

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019