From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-29390-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 31720 invoked by alias); 22 Aug 2007 03:13:14 -0000
Received: (qmail 31522 invoked by uid 22791); 22 Aug 2007 03:13:12 -0000
X-Spam-Check-By: sourceware.org
Received: from romy.inter.net.il (HELO romy.inter.net.il) (213.8.233.24)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 22 Aug 2007 03:13:10 +0000
Received: from HOME-C4E4A596F7 (IGLD-80-230-96-35.inter.net.il [80.230.96.35]) 	by romy.inter.net.il (MOS 3.7.3-GA) 	with ESMTP id IRW15541 (AUTH halo1); 	Wed, 22 Aug 2007 06:12:55 +0300 (IDT)
Date: Wed, 22 Aug 2007 03:13:00 -0000
Message-Id: <ubqd0w9c3.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@codesourcery.com>
CC: Roland.Puntaier@br-automation.com, gdb@sourceware.org
In-reply-to: <m3ejhw4fil.fsf@codesourcery.com> (message from Jim Blandy on 	Tue, 21 Aug 2007 16:46:58 -0700)
Subject: Re: gdb-6.6 mingw port hangs after Ctrl-C
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <OF8E457D60.CC9CEA8E-ONC125733D.005323EA-C125733D.0056FB5E@br-automation.com> 	<20070820162439.GA30242@caradoc.them.org> <u1wdyuidf.fsf@gnu.org> 	<20070820193128.GA17272@caradoc.them.org> 	<20070821025607.GA14389@ednor.casa.cgf.cx> 	<m33aycg4yi.fsf@codesourcery.com> <utzqsu2ly.fsf@gnu.org> <m3ejhw4fil.fsf@codesourcery.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-08/txt/msg00159.txt.bz2

> Cc: Roland.Puntaier@br-automation.com,  gdb@sourceware.org
> From: Jim Blandy <jimb@codesourcery.com>
> Date: Tue, 21 Aug 2007 16:46:58 -0700
> 
> >> The issue at hand here is that we need C-c to interrupt the main
> >> thread as it reads from the remote host.  That could be a pipe, a
> >> socket, or a serial port.
> >> 
> >> Do you know how one can safely interrupt each of these kinds of reads
> >> in Windows?
> >
> > What do you mean by ``safely interrupt''?
> 
> The main thread is in the midst of a 'read' or 'write' operation.  We
> want the thread handling the C-c to be able to make the main thread
> abandon that operation with a suitable indication of why.

Maybe I'm simply unaware of some subtle issues, but I don't know of
any situation where this cannot be done safely.  In particular, the
code I wrote for GNU Make works since the release of Make 3.81, and I
have yet to see any problems with interrupting a running Make, or hear
a single complaint or bug report related to C-c.