From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 8.3 release -- time to start the release process
Date: Sat, 15 Dec 2018 12:55:00 -0000 [thread overview]
Message-ID: <838t0reyqi.fsf@gnu.org> (raw)
In-Reply-To: <20181215122354.GB9867@adacore.com> (message from Joel Brobecker on Sat, 15 Dec 2018 16:23:54 +0400)
> Date: Sat, 15 Dec 2018 16:23:54 +0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> Let's start a list of items we'd like to look into before we branch:
>
> * [JoelB] <NO PR>
> GDB crash or timeout on Windows native
>
> I do not have much information yet, as I haven't had time
> to investigate. But it looks like we're having timeouts
> or crashes. They seem specific to Windows Server 2016,
> and the problem must have appeared between Nov 19th and
> Nov 26th.
>
> My plan is to take a look at it during the Xmas break.
>
> Anything else?
I would like to add this issue:
https://sourceware.org/ml/gdb-patches/2018-12/msg00168.html
Although minor, it should be not too hard to fix, and I'd _really_
like someone to please review my proposals and comment.
Thanks.
prev parent reply other threads:[~2018-12-15 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 12:24 Joel Brobecker
2018-12-15 12:55 ` Eli Zaretskii [this message]
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=838t0reyqi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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