From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1526F3858C5E; Thu, 5 Jan 2023 01:42:55 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1526F3858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672882976; bh=Q1szvCSE50hyKHKYLPJTdmXQ20k6TmsifY8J+w9E9Aw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=yBeTOemdwAD3oYfbzMQZEKh6uapd+s1U/m/tR935k2iQT+/vGlRu44ryvWHAFlOrN +NYl8cY6EBCg6VMIKMN//5CBBRTfiLRSB5XBRah1wQdIzKdDilf6PK5xNT4//yKeFf uQEQZVlVmNzJFLoDd9hA/JsI17jNzCE/FsUuh2SU= From: "simark at simark dot ca" To: gdb-prs@sourceware.org Subject: [Bug gdb/27966] macro tests failing when using -gdwarf-5 -gsplit-dwarf Date: Thu, 05 Jan 2023 01:42:55 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simark at simark dot ca X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D27966 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW --- Comment #3 from Simon Marchi --- (In reply to Tom Tromey from comment #2) > I usually move the bugs to "waiting" when there's a question. > That way when we stumble over it again in N years we know we > can just close it. That's a good idea. However, here I'll move it to NEW (i.e. confirmed), because the main point of the bug is still valid. With the test binary generated with: $ make check TESTS=3Dgdb.base/macscp.exp RUNTESTFLAGS=3D"CC_FOR_TARGET=3Dcl= ang CFLAGS_FOR_TARGET=3D'-gdwarf-5 -gsplit-dwarf'" I get: $ ./gdb -q -nx --data-directory=3Ddata-directory /home/simark/build/binutils-gdb/gdb/testsuite/outputs/gdb.base/macscp/macscp -ex "b macscp2_2" -ex r -ex "info macro WHERE" -batch ... The symbol `WHERE' has no definition as a C/C++ preprocessor macro at /home/simark/src/binutils-gdb/gdb/testsuite/gdb.base/macscp2.h:22 included at /home/simark/src/binutils-gdb/gdb/testsuite/gdb.base/macscp1.= c:1 Whereas with: $ make check TESTS=3Dgdb.base/macscp.exp RUNTESTFLAGS=3D"CC_FOR_TARGET=3Dcl= ang" I get: $ ./gdb -q -nx --data-directory=3Ddata-directory /home/simark/build/binutils-gdb/gdb/testsuite/outputs/gdb.base/macscp/macscp -ex "b macscp2_2" -ex r -ex "info macro WHERE" -batch ... Defined at /home/simark/src/binutils-gdb/gdb/testsuite/gdb.base/macscp2.h:16 included at /home/simark/src/binutils-gdb/gdb/testsuite/gdb.base/macscp1.= c:61 #define WHERE before macscp2_2 --=20 You are receiving this mail because: You are on the CC list for the bug.=