From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 59763 invoked by alias); 4 May 2018 18:30:38 -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 59315 invoked by uid 89); 4 May 2018 18:30:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=risk 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:30:20 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 63746117C7C for ; Fri, 4 May 2018 14:30:04 -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 9sqOouZh8G7G for ; Fri, 4 May 2018 14:30:04 -0400 (EDT) Received: from tron.gnat.com (tron.gnat.com [IPv6:2620:20:4000:0:46a8:42ff:fe0e:e294]) by rock.gnat.com (Postfix) with ESMTP id 53A12117C7B for ; Fri, 4 May 2018 14:30:04 -0400 (EDT) Received: by tron.gnat.com (Postfix, from userid 4233) id 50000487; Fri, 4 May 2018 14:30:04 -0400 (EDT) From: Joel Brobecker To: gdb-patches@sourceware.org Subject: [Windows GDBserver] Make GDBserver functional again on Windows Date: Fri, 04 May 2018 18:30:00 -0000 Message-Id: <1525458603-33351-1-git-send-email-brobecker@adacore.com> X-SW-Source: 2018-05/txt/msg00122.txt.bz2 Hello, 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 [PATCH 3/3] gdbserver/Windows: crash during connection establishment 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 only quickly experimented with GDBserver 8.1, but I think it's completely broken then as well :-(. Some of the fixes might be applicable there. I will double-check -- also as soon as I have a moment, and for sure before we release 8.1.1. Thanks, -- Joel