From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 64590 invoked by alias); 9 Sep 2018 18:36:49 -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 64581 invoked by uid 89); 9 Sep 2018 18:36:48 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=benefits, dig, complaints, consequences X-HELO: gateway31.websitewelcome.com Received: from gateway31.websitewelcome.com (HELO gateway31.websitewelcome.com) (192.185.143.36) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 09 Sep 2018 18:36:46 +0000 Received: from cm14.websitewelcome.com (cm14.websitewelcome.com [100.42.49.7]) by gateway31.websitewelcome.com (Postfix) with ESMTP id 5C093273A3 for ; Sun, 9 Sep 2018 13:36:45 -0500 (CDT) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with SMTP id z4ZhfX024kBj6z4Zhfig2Q; Sun, 09 Sep 2018 13:36:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=YWnsqs/LaR/CmzqH2fcfS3P//HY6LMRkrW25HV3bGOQ=; b=KEp95J54SAibmDvr9OY27PtH0X C+c+FcWAqemFDSMNh+7awPTrJy/DiipPs90zwCkNE1bhLuTHbKRnKIEHVYnN1zLc67xQbARh4LDpc wlnuB4LcXfaxrO11ijJ2WaFVW; Received: from 75-166-85-72.hlrn.qwest.net ([75.166.85.72]:44190 helo=bapiya) by box5379.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1fz4Zh-002kFQ-3m; Sun, 09 Sep 2018 13:36:45 -0500 From: Tom Tromey To: Eli Zaretskii Cc: gdb-patches@sourceware.org, mjw@redhat.com Subject: Re: [ANNOUNCEMENT] GDB 8.2 released! References: <83ftyjq90h.fsf@gnu.org> Date: Sun, 09 Sep 2018 18:36:00 -0000 In-Reply-To: <83ftyjq90h.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 09 Sep 2018 13:07:26 +0300") Message-ID: <87in3e4iwz.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2018-09/txt/msg00240.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: CCing Mark Wielaard -- Mark see about 3/4 down... Eli> Building GDB 8.2 with MinGW GCC 7.3.0 on MS-Windows, I see a warning: Eli> CXX record-btrace.o Eli> In file included from exceptions.h:23:0, Eli> from utils.h:24, Eli> from defs.h:666, Eli> from record-btrace.c:22: Eli> 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)': Eli> ui-out.h:197: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); Eli> ~~~~~~~~~~~~~^~~~~~ Eli> record-btrace.c:792:35: note: 'asm_list.ui_out_emit_type<(ui_out_type)1>::m_uiout' was declared here Eli> gdb::optional asm_list; Eli> ^~~~~~~~ Eli> Is this a real problem? No, I think this is a false positive from gcc. You may want to file a gcc bug though I feel like there may be one already. Eli> Also, a couple of places in remote-fileio.c use gettimeofday, which I Eli> believe is deprecated under the recent versions of Posix; the Eli> recommended replacement is clock_gettime. Please file a bug. I don't know how important this is or whether we still care about porting to systems without that. Maybe gnulib can help here. Eli> During symbol reading, unsupported tag: 'DW_TAG_unspecified_type'. We discussed this one before. It's a mild gdb bug. Probably no consequences. Eli> During symbol reading, macro `WCHAR_MIN' redefined at d:/usr/include/wchar.h:70; Eli> original definition at build-gnulib/import/stdint.h:561. Eli> During symbol reading, macro `WCHAR_MAX' redefined at d:/usr/include/wchar.h:71; Eli> original definition at build-gnulib/import/stdint.h:563. Maybe a gcc bug. Eli> During symbol reading, const value length mismatch for 'std::ratio<1, 1000000000>::num', got 8, expected 0. gcc bug. Eli> During symbol reading, Member function "~_Sp_counted_base" (offset 0x3f07e1) is virtual but the vtable offset is not specified. We discussed this one before, too. Longstanding gcc bug with no agreed upon approach to resolving it. I think my preferred approach would be for g++ to emit DWARF describing the virtual table in its entirety. This would let gdb know a bit less about the ABI and would also maybe have some other benefits. This is the path we're heading down for Rust. Eli> During symbol reading, cannot get low and high bounds for subprogram DIE at 0x40c43e. Eli> During symbol reading, Child DIE 0x4433a0 and its abstract origin 0x448aff have different parents. Eli> During symbol reading, No DW_FORM_block* DW_AT_call_value for DW_TAG_call_site child DIE 0x447010 [in module D:\gnu\gdb-8.2\gdb\gdb.exe]. Eli> During symbol reading, Multiple children of DIE 0x448d3a refer to DIE 0x448a80 as their abstract origin. Eli> During symbol reading, DIE 0x44aa21 and its abstract origin 0x446e69 have different tags. I don't know about these. Many times these complaints are due to DWARF oddities, but I feel there are some complaints that represent gdb limitations. So you have to dig to find out. I think most of these things would be good things for dwarflint to check. (Hi Mark.) Eli> Anything here I should worry about? Probably not. Eli> Running "make -C gdb install-strip" fails: Eli> /bin/sh /d/gnu/gdb-8.2/install-sh -c -s ./contrib/gdb-add-index.sh \ Eli> d:/usr/test-gdb-8.2/bin/$transformed_name.exe Eli> d:\usr\bin\strip.exe:d:/usr/test-gdb-8.2/bin/_inst.8116_: file format not recognized Eli> It fails because Makefile attempts to invoke 'strip' on a shell Eli> script. I couldn't find any way to get past that except by hacking Eli> gdb/Makefile to remove the offending portion, then installing that Eli> shell script manually. How does this work on Posix hosts? gdb defines: INSTALL_SCRIPT = @INSTALL_SCRIPT@ ... but install-only does not use it for gdb-add-index.sh. I think this is just a bug. It is used properly for gcore. I didn't try the obvious patch, but maybe you could? Tom