Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Windows GDBserver] Make GDBserver functional again on Windows
Date: Fri, 04 May 2018 18:54:00 -0000	[thread overview]
Message-ID: <20180504185431.3hclnf4io4kl7daf@adacore.com> (raw)
In-Reply-To: <878t8z5km9.fsf@redhat.com>

> > 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


  reply	other threads:[~2018-05-04 18:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 18:30 Joel Brobecker
2018-05-04 18:30 ` [PATCH 2/3] gdbserver/Windows: Fix "no program to debug" error Joel Brobecker
2018-05-10  0:09   ` Pedro Alves
2018-05-10 16:50     ` Joel Brobecker
2018-05-04 18:30 ` [PATCH 3/3] gdbserver/Windows: crash during connection establishment phase Joel Brobecker
2018-05-04 18:46   ` Pedro Alves
2018-05-04 18:58     ` Joel Brobecker
2018-05-04 19:12       ` Pedro Alves
2018-05-07 21:47         ` Joel Brobecker
2018-05-09 15:54           ` Pedro Alves
2018-05-09 23:09             ` Joel Brobecker
2018-05-09 23:17               ` Pedro Alves
2018-05-10 17:04             ` Joel Brobecker
2018-05-04 20:20   ` Eli Zaretskii
2018-05-04 18:30 ` [PATCH 1/3] [gdbserver/win32] fatal "glob could not process pattern '(null)'" error Joel Brobecker
2018-05-09 23:50   ` Pedro Alves
2018-05-10 16:48     ` Joel Brobecker
2018-05-04 18:41 ` [Windows GDBserver] Make GDBserver functional again on Windows Sergio Durigan Junior
2018-05-04 18:54   ` Joel Brobecker [this message]
2018-05-10 18:19 ` Joel Brobecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180504185431.3hclnf4io4kl7daf@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox