public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jankowski938 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/25209] "A problem internal to GDB has been detected" (ARM) complex .elf file
Date: Thu, 31 Mar 2022 02:12:03 +0000 [thread overview]
Message-ID: <bug-25209-4717-fxISgCjj4X@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25209-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25209
--- Comment #6 from jankowski938 at gmail dot com ---
Now have this problem with 8.3 (2020)
[New Remote target]
/build/gnu-tools-for-stm32_9-2020-q2-update.20201001-1621/src/gdb/gdb/gdbtypes.c:4994:
internal-error: type* copy_type(const type*): Assertion `TYPE_OBJFILE_OWNED
(type)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session?
This is a bug, please report it.(y or n) [answered Y; input not from terminal]
/build/gnu-tools-for-stm32_9-2020-q2-update.20201001-1621/src/gdb/gdb/gdbtypes.c:4994:
internal-error: type* copy_type(const type*): Assertion `TYPE_OBJFILE_OWNED
(type)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]
For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2022-03-31 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25209-4717@http.sourceware.org/bugzilla/>
2022-03-31 2:12 ` jankowski938 at gmail dot com [this message]
2022-03-31 20:34 ` tromey at sourceware dot org
2022-06-05 17:25 ` tromey at sourceware dot 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-25209-4717-fxISgCjj4X@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).