Bug 24925 - internal-error: void add_separate_debug_objfile(objfile*, objfile*): Assertion `parent->separate_debug_objfile_backlink == NULL' failed
Summary: internal-error: void add_separate_debug_objfile(objfile*, objfile*): Assertio...
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: python (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-21 13:35 UTC by Tom de Vries
Modified: 2023-12-16 15:42 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments
Add target board gdb/testsuite/boards/cc-with-gnu-debuglink.exp (1.14 KB, patch)
2019-08-21 13:35 UTC, Tom de Vries
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Tom de Vries 2019-08-21 13:35:14 UTC
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)
...
Comment 1 Tom de Vries 2019-09-30 07:16:54 UTC
(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.
Comment 3 Hannes Domani 2023-12-16 15:08:55 UTC
(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.
Comment 4 Tom de Vries 2023-12-16 15:42:05 UTC
(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.