From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 44EC43858298; Wed, 23 Nov 2022 11:59:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 44EC43858298 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1669204781; bh=g2NeavBWM1VEoi+3bZTNjzQWOt9aym5xA2hJfKImXAM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ltTaKr5WlbneKjZGue3bwFq62Rb7rUJ5uDWai980S+FUiWLdPamvnYyJtzSU2ZmhS //yrx/WD1rV9JtHAD9dAv4FUe/PVEk48cfQSNytc+jYuvwzMJonRZTWgJMalcJCTBo PKf1gEQIu+Ulz3it4ewKvOtZURdwtEa3M5u+nXQA= From: "uweigand at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug tdep/29814] [gdb/tdep, powerpc64le] FAIL: gdb.base/msym-bp-shl.exp: debug=0: before run: info breakpoint Date: Wed, 23 Nov 2022 11:59:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: uweigand 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: cc 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=3D29814 Ulrich Weigand changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |uweigand at gcc dot gnu.org --- Comment #4 from Ulrich Weigand --- This fix seems wrong. The symbol should have been marked as having no local entry point (i.e. fun.minsym->target_flag_1 () should have returned 0). You should check why that doesn't happen - what does ppc_elfv2_elf_make_msymbol_special do for this symbol? Is this a "real" symbol, or is it one of the synthetic symbols generated by BFD? In the latter case, either ...make_msybol_special doesn't handle those correctly, or the symbol is synthesized using wrong flags. --=20 You are receiving this mail because: You are on the CC list for the bug.=