From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 39894 invoked by alias); 4 May 2018 18:54:36 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 39885 invoked by uid 89); 4 May 2018 18:54:36 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=risk, our X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 04 May 2018 18:54:35 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id DE9F71176AE; Fri, 4 May 2018 14:54:33 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id vYFobI6oNslN; Fri, 4 May 2018 14:54:33 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id AD2D61176A3; Fri, 4 May 2018 14:54:33 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id F26D983055; Fri, 4 May 2018 11:54:31 -0700 (PDT) Date: Fri, 04 May 2018 18:54:00 -0000 From: Joel Brobecker To: Sergio Durigan Junior Cc: gdb-patches@sourceware.org Subject: Re: [Windows GDBserver] Make GDBserver functional again on Windows Message-ID: <20180504185431.3hclnf4io4kl7daf@adacore.com> References: <1525458603-33351-1-git-send-email-brobecker@adacore.com> <878t8z5km9.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <878t8z5km9.fsf@redhat.com> User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2018-05/txt/msg00134.txt.bz2 > > I noticed a few weeks back that GDBserver on Windows was no longer > > functional, so I started working on it as time allowed. With the > > following patches, it's mostly functional, as in I only have few > > regressions left. I wanted to have clean results before submitting, > > but a recent patch showed that waiting could cause others to duplicate > > something I had already done, so I'm posting now. The worse that can > > happen is that I realize an earlier patch has a bug shown by the current > > regressions, or that one of my patches is incomplete, but I think > > it would be nothing compared to the risk of having work being duplicated. > > > > [PATCH 1/3] [gdbserver/win32] fatal "glob could not process pattern > > [PATCH 2/3] gdbserver/Windows: Fix "no program to debug" error > > Thanks for the patches. The first two in the series fix issues > introduced by some modifications I've made, and I apologize for that. Thanks for having looked at the patches. No need to apologize for breaking stuff -- it's just something that is so easy to do that all of us do it despite our best efforts. > > I haven't analyzed all the remaining failures yet, but most of them > > seem to be related to the "kill" command not working. I will look > > into that as soon as I have a moment (but it is looking like it may > > be a week before I have the time). > > I wonder if the failures have something to do with the recent > modifications I've made on 'set print inferior-events' and the messages > printed when the inferior is killed. Anyway, something to keep in mind. It's unfortunately really broken. killing fails with an error (that I don't remember). -- Joel