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 python/24925] internal-error: void add_separate_debug_objfile(objfile*, objfile*): Assertion `parent->separate_debug_objfile_backlink == NULL' failed
Date: Sat, 16 Dec 2023 15:42:05 +0000 [thread overview]
Message-ID: <bug-24925-4717-p4R5p1jssD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24925-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24925
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(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.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-12-16 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-24925-4717@http.sourceware.org/bugzilla/>
2022-10-12 15:23 ` vries at gcc dot gnu.org
2023-12-16 15:08 ` ssbssa at sourceware dot org
2023-12-16 15:42 ` vries at gcc dot gnu.org [this message]
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-24925-4717-p4R5p1jssD@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).