From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9411 invoked by alias); 15 Dec 2018 12:55:10 -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 9376 invoked by uid 89); 15 Dec 2018 12:55:09 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:834 X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (208.118.235.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 15 Dec 2018 12:55:07 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gY9TB-0000WP-RD for gdb-patches@sourceware.org; Sat, 15 Dec 2018 07:55:06 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:46828) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gY9TB-0000WH-M0; Sat, 15 Dec 2018 07:55:01 -0500 Received: from [176.228.60.248] (port=1503 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gY9TB-00074m-9e; Sat, 15 Dec 2018 07:55:01 -0500 Date: Sat, 15 Dec 2018 12:55:00 -0000 Message-Id: <838t0reyqi.fsf@gnu.org> From: Eli Zaretskii To: Joel Brobecker CC: gdb-patches@sourceware.org In-reply-to: <20181215122354.GB9867@adacore.com> (message from Joel Brobecker on Sat, 15 Dec 2018 16:23:54 +0400) Subject: Re: GDB 8.3 release -- time to start the release process References: <20181215122354.GB9867@adacore.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-IsSubscribed: yes X-SW-Source: 2018-12/txt/msg00170.txt.bz2 > Date: Sat, 15 Dec 2018 16:23:54 +0400 > From: Joel Brobecker > > Let's start a list of items we'd like to look into before we branch: > > * [JoelB] > 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.