From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id 6E22D3858D28 for ; Sat, 26 Mar 2022 18:51:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 6E22D3858D28 Received: from [2001:470:142:3::e] (port=58986 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nYBVv-00024J-RB; Sat, 26 Mar 2022 14:51:52 -0400 Received: from [87.69.77.57] (port=1296 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nYBVv-000893-Ah; Sat, 26 Mar 2022 14:51:51 -0400 Date: Sat, 26 Mar 2022 21:51:49 +0300 Message-Id: <83o81sa6nu.fsf@gnu.org> From: Eli Zaretskii To: brobecker@adacore.com CC: gdb-patches@sourceware.org In-Reply-To: <83pmm8a7gn.fsf@gnu.org> (message from Eli Zaretskii via Gdb-patches on Sat, 26 Mar 2022 21:34:32 +0300) Subject: Re: GDB 12.0.90 available for testing References: <20220320055815.2A90FA4D6C@takamaka.home> <83sfr4a93r.fsf@gnu.org> <83pmm8a7gn.fsf@gnu.org> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_00, BODY_8BITS, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2022 18:51:54 -0000 > Date: Sat, 26 Mar 2022 21:34:32 +0300 > X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00, BODY_8BITS, > DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, > RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, > T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 > From: Eli Zaretskii via Gdb-patches > Cc: gdb-patches@sourceware.org > > > Date: Sat, 26 Mar 2022 20:59:04 +0300 > > From: Eli Zaretskii via Gdb-patches > > Cc: gdb-patches@sourceware.org > > > > First, there's this compilation warning when compiling infrun.c: > > > > CXX infrun.o > > In file included from btrace.h:30, > > from gdbthread.h:29, > > from infrun.h:21, > > from infrun.c:23: > > target/waitstatus.h: In function 'void stop_all_threads()': > > target/waitstatus.h:175:13: warning: 'ws.target_waitstatus::m_value' may be used uninitialized in this function [-Wmaybe-uninitialized] > > 175 | m_value = other.m_value; > > | ~~~~~~~~^~~~~~~~~~~~~~~ > > > > Is this a real problem? > > > > Second, one of the selftests fails: > > > > Running selftest dw2_expand_symtabs_matching. > > warning: charset conversion failure for 'u8fun├º├úo'. > > You may have the wrong value for 'set ada source-charset'. > > warning: could not convert 'yfunc ' from the host encoding (CP1255) to UTF-32. > > This normally should not happen, please file a bug report. > > > > AFAIU, this is because the names of these two functions are, > > respectively, in UTF-8 and in Latin-1, but the charset conversion > > thinks they are in CP1255. Where does the test tell the conversion > > functions what is the source encoding? > > And another problem: starting this GDB under Emacs, with "M-x gdb" > (which invokes "gdb -i=mi") seems to confuse Emacs, so much so that > the debugging session is barely usable: symbols are unknown, so I > cannot set breakpoints, etc. And yet another issue: if I start GDB with the MI interface: gdb -i=mi PROGRAM then whatever I type at the prompt GDB thinks I typed "g": (gdb) r -Q &"g\n" &"Ambiguous command \"g\": gcore, generate-core-file, goto-bookmark, gr, gu, guile, guile-repl.\n" ^error,msg="Ambiguous command \"g\": gcore, generate-core-file, goto-bookmark, gr, gu, guile, guile-repl." (gdb) As you see, I typed "r -Q", but GDB thinks I typed "g". Any idea how to debug this? (There's no such problem if I invoke GDB with the CLI interpreter.)