From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32488 invoked by alias); 16 Dec 2019 18:52:08 -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 32476 invoked by uid 89); 16 Dec 2019 18:52:08 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-17.3 required=5.0 tests=AWL,BAYES_00,ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_PASS,USER_IN_DEF_SPF_WL autolearn=ham version=3.3.1 spammy=our X-HELO: mail-ot1-f47.google.com Received: from mail-ot1-f47.google.com (HELO mail-ot1-f47.google.com) (209.85.210.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 16 Dec 2019 18:52:07 +0000 Received: by mail-ot1-f47.google.com with SMTP id i15so10338760oto.7 for ; Mon, 16 Dec 2019 10:52:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=V3KmXpDBxhIPTaQK8B/NOqHz0P5Be0cxdjhrZn38t5A=; b=QOV8dav7fVq0qEXKIVQiIRhXrU2BP/kMTycIpCYxkCqR9IpuFJGoIW107TB/VZWdMT Z1ptpF08jUz6w32oiIJDykBqhIzQAQObw9THSZIOdR9SvYA5JVPgNYpZGZq58qRC9xhg 5GHlM/FI9WjZn8s1W6FB9hPPJSxFv7/Pp30ZuLn0tpOip7HzAJcnpBBMIbLbjGN3tyhU +tSkQjtG+2mhcRMcYjfUyjqairRl9NNgMXdSVoaV4p46lhzJ2zUKL0VF/KPIwaqsx1B/ eIYE25PQyGEL7/3VGiUlv06lt9xnTaoAcNTVP1eftPxHWLdW3K3xhIOZrH9CFbqRt8tG w/5Q== MIME-Version: 1.0 References: <20191211214745.E1CF0838D4@joel.gnat.com> <83tv604239.fsf@gnu.org> In-Reply-To: <83tv604239.fsf@gnu.org> From: "Christian Biesinger via gdb-patches" Reply-To: Christian Biesinger Date: Mon, 16 Dec 2019 18:52:00 -0000 Message-ID: Subject: Re: GDB 9.0.90 available for testing To: Eli Zaretskii Cc: Joel Brobecker , gdb-patches Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00713.txt.bz2 On Mon, Dec 16, 2019 at 11:23 AM Eli Zaretskii wrote: > 2. readline/colors.c fails to compile because it uses the likes of > S_IXGRP and S_IXOTH, which aren't defined in MinGW. The solution > is to patch readline/posixstat.h to add the missing defines (it > tries to do so, but makes assumptions that don't do a perfect job). I don't see either of those two used in colors.c? > 5. A compilation warning in gdb/, which wasn't there in GDB 8.3: > > CXX record-btrace.o > In file included from ../../gdb-9.0.90/gdb/exceptions.h:23, > from ../../gdb-9.0.90/gdb/utils.h:24, > from ../../gdb-9.0.90/gdb/defs.h:652, > from ../../gdb-9.0.90/gdb/record-btrace.c:22: > ../../gdb-9.0.90/gdb/ui-out.h: In function 'void btrace_insn_history(ui_out*, const btrace_thread_info*, const btrace_insn_iterator*, const btrace_insn_iterator*, gdb_disassembly_flags)': > ../../gdb-9.0.90/gdb/ui-out.h:349:18: warning: 'asm_list.ui_out_emit_type<(ui_out_type)1>::m_uiout' may be used uninitialized in this function [-Wmaybe-uninitialized] > m_uiout->end (Type); > ~~~~~~~~~~~~~^~~~~~ > ../../gdb-9.0.90/gdb/record-btrace.c:779:35: note: 'asm_list.ui_out_emit_type<(ui_out_type)1>::m_uiout' was declared here > gdb::optional asm_list; > ^~~~~~~~ > > Any suggestions how to fix this? I see this on Linux too, fwiw. I assumed everyone saw it... > Please tell me how to go about fixing these problems on the release > branch. Do we still maintain our separate copy of Readline, or do I > need to report to its upstream maintainer? And what to do about > libctf? how can I speed up the handling of those problems upstream? I've had some success in sending a bug report/patch to upstream readline. Not sure about ctf. Christian