From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19615 invoked by alias); 21 Apr 2005 21:15:44 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 19471 invoked from network); 21 Apr 2005 21:15:36 -0000 Received: from unknown (HELO mail.codesourcery.com) (65.74.133.9) by sourceware.org with SMTP; 21 Apr 2005 21:15:36 -0000 Received: (qmail 898 invoked from network); 21 Apr 2005 21:15:35 -0000 Received: from localhost (HELO ?192.168.0.2?) (mitchell@127.0.0.1) by mail.codesourcery.com with SMTP; 21 Apr 2005 21:15:35 -0000 Message-ID: <426817F0.5070404@codesourcery.com> Date: Thu, 21 Apr 2005 21:15:00 -0000 From: Mark Mitchell Organization: CodeSourcery, LLC User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: Daniel Jacobowitz CC: Eli Zaretskii , gdb-patches@sources.redhat.com Subject: Re: PATCH: Support Windows in event-loop.c References: <200504210549.j3L5n2nP027728@sirius.codesourcery.com> <01c546a1$Blat.v2.4$e03250c0@zahav.net.il> <4267F742.2090108@codesourcery.com> <01c546b0$Blat.v2.4$c193bb40@zahav.net.il> <20050421205617.GA13146@nevyn.them.org> In-Reply-To: <20050421205617.GA13146@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-04/txt/msg00263.txt.bz2 Daniel Jacobowitz wrote: > Anyway, if Mark can come up with a select wrapper, then maybe we can > drop the question entirely. I'm sure I can, if that's the only way to get this functionality into GDB. But, the emacs select wrapper is hardly a full implementation of select; for example, it only handles file descriptors waiting for "read", not "write". To me, adding a partial emulation of a POSIX function, without real POSIX semantics and behavior, is confusing. And adding a full emulation is going to be a lot more code than the present change -- and will perform worse to boot. Windows isn't UNIX, and waiting for activity on file descriptors is one of the places where Windows made some rather different choices. This is a low-level system-programming code, and so system details appear. It's like dealing with different rules for interruptable syscalls, different signal-handling rules, and so forth. Fortunately, it doesn't look like event-loop.c is a very active area of development. It looks like the last substantive change was on 2002-05-14. It seems unlikely to me that this change is going to make it a lot harder for people to make other improvements to event-loop.c. -- Mark Mitchell CodeSourcery, LLC mark@codesourcery.com (916) 791-8304