From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 430 invoked by alias); 22 Aug 2007 10:13:50 -0000 Received: (qmail 32669 invoked by uid 22791); 22 Aug 2007 10:13:46 -0000 X-Spam-Check-By: sourceware.org Received: from mail.artimi.com (HELO mail.artimi.com) (194.72.81.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 22 Aug 2007 10:13:37 +0000 Received: from rainbow ([192.168.8.46]) by mail.artimi.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 22 Aug 2007 11:13:34 +0100 From: "Dave Korn" To: "'Eli Zaretskii'" , "'Jim Blandy'" Cc: , References: <20070820162439.GA30242@caradoc.them.org> <20070820193128.GA17272@caradoc.them.org> <20070821025607.GA14389@ednor.casa.cgf.cx> Subject: RE: gdb-6.6 mingw port hangs after Ctrl-C Date: Wed, 22 Aug 2007 10:13:00 -0000 Message-ID: <009a01c7e4a4$fdd913e0$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-08/txt/msg00161.txt.bz2 On 22 August 2007 04:13, Eli Zaretskii wrote: >> Cc: Roland.Puntaier@br-automation.com, gdb@sourceware.org >> From: Jim Blandy >> 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. I'd be curious to take a look at that, can you point me at the right part of the sources? cheers, DaveK -- Can't think of a witty .sigline today....