Created attachment 11958 [details] Add target board gdb/testsuite/boards/cc-with-gnu-debuglink.exp Using the attachment (that adds a target board gdb/testsuite/boards/cc-with-gnu-debuglink.exp) we get for: ... $ ( cd build/gdb/testsuite/; make check RUNTESTFLAGS="gdb.python/py-objfile.exp --target_board=cc-with-gnu-debuglink" ) ... this internal error: ... (gdb) PASS: gdb.python/py-objfile.exp: print main without debug info python objfile.add_separate_debug_file("/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.python/py-objfile/py-objfile")^M /data/gdb_versions/devel/src/gdb/objfiles.c:543: internal-error: void add_separate_debug_objfile(objfile*, objfile*): Assertion `parent->separate_debug_objfile_backlink == NULL' failed.^M A problem internal to GDB has been detected,^M further debugging may prove unreliable.^M Quit this debugging session? (y or n) FAIL: gdb.python/py-objfile.exp: Add separate debug file file (GDB internal error) ...
(In reply to Tom de Vries from comment #0) > Created attachment 11958 [details] > Add target board gdb/testsuite/boards/cc-with-gnu-debuglink.exp Filed an enhancement PR for it: PR25047.
submitted: https://sourceware.org/pipermail/gdb-patches/2022-October/192608.html
(In reply to Tom de Vries from comment #2) > submitted: > https://sourceware.org/pipermail/gdb-patches/2022-October/192608.html That patch was committed some time ago, so can this be closed? On the other hand, it mentions only PR29277, so I'm not sure this is even related.
(In reply to Hannes Domani from comment #3) > (In reply to Tom de Vries from comment #2) > > submitted: > > https://sourceware.org/pipermail/gdb-patches/2022-October/192608.html > > That patch was committed some time ago, so can this be closed? > On the other hand, it mentions only PR29277, so I'm not sure this is even > related. I can still reproduce this internal error, so mentioning the patch might have been a mistake, I'm not sure.