From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 118931 invoked by alias); 16 Dec 2019 17:23:12 -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 118919 invoked by uid 89); 16 Dec 2019 17:23:12 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=thusly, H*r:142, likes, 8.3 X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 16 Dec 2019 17:23:10 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:34646) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1igu5K-0006z3-Tb; Mon, 16 Dec 2019 12:23:08 -0500 Received: from [176.228.60.248] (port=4147 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1igu5K-00079y-6n; Mon, 16 Dec 2019 12:23:06 -0500 Date: Mon, 16 Dec 2019 17:23:00 -0000 Message-Id: <83tv604239.fsf@gnu.org> From: Eli Zaretskii To: Joel Brobecker CC: gdb-patches@sourceware.org In-reply-to: <20191211214745.E1CF0838D4@joel.gnat.com> (message from Joel Brobecker on Wed, 11 Dec 2019 22:47:45 +0100 (CET)) Subject: Re: GDB 9.0.90 available for testing References: <20191211214745.E1CF0838D4@joel.gnat.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00706.txt.bz2 > From: Joel Brobecker > Date: Wed, 11 Dec 2019 22:47:45 +0100 (CET) > > > ftp://sourceware.org/pub/gdb/snapshots/branch/gdb-9.0.90.tar.xz > > A gzip'ed version is also available: gdb-9.0.90.tar.gz. > > Please give it a test if you can and report any problems you might find. I've built this with mingw.org's MinGW, using GCC 8.3.0 and Binutils 2.33, and found the following issues: 1. The produced gdb.exe and gdbserver.exe depend on the libstdc++ and libgcc DLLs. I thought this was supposed to be prevented, or did I dream? Should I force -static-libgcc etc. switches via configure-time variables? 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). 3. When configure runs in gdb/, it displays a warning thusly: checking for pthread-config... no /d/usr/eli/utils/gdb-9.0.90/gdb/configure: line 14342: test: =: unary operator expected It is triggered by this line: if test $gdb_cv_cxx_std_thread = yes; then but I have no idea what's wrong with this. Any hints? 4. libctf fails to compile due to 3 compilation errors. I already found these problems when building Binutils 2.33 and reported them on Bugzilla (https://sourceware.org/bugzilla/show_bug.cgi?id=25155), but it seems nothing was done about that in the meantime. 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? 6. One last comment about "gdb -tui": while stepping with "next" through a program (in this case, GDB's only binary), sometimes the source window becomes blank and shows only "No source" in it. This happens when the command windo shows some DWARF-related error message. Is this expected? I don't think I saw this in previous versions of GDB. 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? Thanks.