From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5905A3858439; Tue, 19 Jul 2022 14:23:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5905A3858439 From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/29277] jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed with separate debug files Date: Tue, 19 Jul 2022 14:23:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: Tue, 19 Jul 2022 14:23:25 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D29277 --- Comment #2 from Tom de Vries --- It would be nice if you could post a reproducer. AFAIU, a reproducer would trigger this assert: ... diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c index 74f53368464..fb4d58fa66d 100644 --- a/gdb/breakpoint.c +++ b/gdb/breakpoint.c @@ -5668,6 +5668,7 @@ handle_jit_event (CORE_ADDR address) function needs to be updated too. */ bound_minimal_symbol jit_bp_sym =3D lookup_minimal_symbol_by_pc (address= ); gdb_assert (jit_bp_sym.objfile !=3D nullptr); + gdb_assert (jit_bp_sym.objfile->separate_debug_objfile_backlink =3D=3D n= ullptr); jit_event_handler (gdbarch, jit_bp_sym.objfile); target_terminal::inferior (); ... but I haven't been able to, when runnning the gdb.base/jit-*.exp test-cases using target board cc-with-gnu-debuglink, which was my best bet. Alternatively, can you explain why we end up here with jit_bp_sym.objfile->separate_debug_objfile_backlink !=3D nullptr? AFAIU, t= he fix from PR27889 should prevent that from occurring. Is there something peculiar about the executable / separate debug file combination? Can you post a readelf -S for both (or even better, if possib= le, attach or post them in some dropbox format)? --=20 You are receiving this mail because: You are on the CC list for the bug.=