[Bug breakpoints/29277] jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed with separate debug files

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29277

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
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 = lookup_minimal_symbol_by_pc (address);
   gdb_assert (jit_bp_sym.objfile != nullptr);
+  gdb_assert (jit_bp_sym.objfile->separate_debug_objfile_backlink == nullptr);
   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 != nullptr?  AFAIU, the 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 possible,
attach or post them in some dropbox format)?

-- 
You are receiving this mail because:
You are on the CC list for the bug.