public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/29277] jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed with separate debug files
Date: Mon, 01 Aug 2022 15:56:41 +0000 [thread overview]
Message-ID: <bug-29277-4717-44cD3DuT5h@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29277-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29277
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
Fixed by:
...
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index dae96d205be..4ea22f4bd9c 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -5669,7 +5669,10 @@ handle_jit_event (CORE_ADDR address)
function needs to be updated too. */
bound_minimal_symbol jit_bp_sym = lookup_minimal_symbol_by_pc (address);
gdb_assert (jit_bp_sym.objfile != nullptr);
- jit_event_handler (gdbarch, jit_bp_sym.objfile);
+ objfile *objfile = jit_bp_sym.objfile;
+ if (objfile->separate_debug_objfile_backlink)
+ objfile = objfile->separate_debug_objfile_backlink;
+ jit_event_handler (gdbarch, objfile);
target_terminal::inferior ();
}
...
which is essentially a refactoring of the patch from comment 1.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-01 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 19:20 [Bug breakpoints/29277] New: " guillaume at morinfr dot org
2022-06-23 13:44 ` [Bug breakpoints/29277] " vries at gcc dot gnu.org
2022-06-27 14:06 ` hector.oron at gmail dot com
2022-07-19 14:23 ` vries at gcc dot gnu.org
2022-08-01 13:46 ` schwab@linux-m68k.org
2022-08-01 15:55 ` vries at gcc dot gnu.org
2022-08-01 15:56 ` vries at gcc dot gnu.org [this message]
2022-08-01 16:46 ` vries at gcc dot gnu.org
2022-10-13 13:40 ` vries at gcc dot gnu.org
2023-12-16 15:24 ` ssbssa at sourceware dot org
2023-12-16 15:36 ` vries at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-29277-4717-44cD3DuT5h@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).