From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 57C7F385783A; Mon, 5 Apr 2021 14:17:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 57C7F385783A From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug corefiles/27689] FAIL: gdb.base/gcore-tls-pie.exp: x/i $pc Date: Mon, 05 Apr 2021 14:17:15 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org 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: 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 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Apr 2021 14:17:15 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D27689 --- Comment #1 from Tom de Vries --- (In reply to Tom de Vries from comment #0) > warning: core file may not match specified executable file.^M I looked into this warning. It's due to a mismatch in buildid, which is ca= used by incorrect reading of the buildid for the core. We're trying to read the following 3 notes from the core: ... 04 00 00 00 10 00 00 00 01 00 00 00 |o.2...........= ..| 00000770 47 4e 55 00 00 00 00 00 03 00 00 00 02 00 00 00 |GNU...........= ..| 00000780 00 00 00 00 00 00 00 00 04 00 00 00 20 00 00 00 |............ .= ..| 00000790 05 00 00 00 47 4e 55 00 02 80 00 c0 04 00 00 00 |....GNU.......= ..| 000007a0 01 00 00 00 00 00 00 00 01 00 01 c0 04 00 00 00 |..............= ..| 000007b0 01 00 00 00 00 00 00 00 04 00 00 00 14 00 00 00 |..............= ..| 000007c0 03 00 00 00 47 4e 55 00 79 c4 e9 5a c4 c0 5c ce |....GNU.y..Z..= \.| 000007d0 95 e9 38 e2 13 58 41 4e 2e fa 5f c7 ... [ Note format: First word is name size (4 in all cases), second words is da= ta size (0x10, 0x20 and 0x14), third word is type (1,5,3, see NT_GNU constants= in include/elf/common.h), then there's the name, "GNU\0", followed by the data= . ] First we have a NT_GNU_ABI_TAG note, then a NT_GNU_PROPERTY_TYPE_0 note, th= en a NT_GNU_BUILD_ID note. However, the NT_GNU_PROPERTY_TYPE_0 note has alignment 8: ...=20 [Nr] Name Type Address Off Size ES = Flg Lk Inf Al ... [16] .note.gnu.property NOTE 0000000000000000 000390 000030 00= A 0 0 8 ... to it doesn't start immediately after the NT_GNU_ABI_TAG note, instead we h= ave 4 bytes padding (00 00 00 00). The padding throws off the note reader in bfd, so the last two notes are not read correctly. --=20 You are receiving this mail because: You are on the CC list for the bug.=