public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "emr-gnu at hev dot psu.edu" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28801] New: "gdb/gdbtypes.h:441: internal-error: LONGEST dynamic_prop::const_val() const: Assertion `m_kind == PROP_CONST' failed" when listing functions Date: Thu, 20 Jan 2022 19:56:01 +0000 [thread overview] Message-ID: <bug-28801-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28801 Bug ID: 28801 Summary: "gdb/gdbtypes.h:441: internal-error: LONGEST dynamic_prop::const_val() const: Assertion `m_kind == PROP_CONST' failed" when listing functions Product: gdb Version: 11.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: emr-gnu at hev dot psu.edu Target Milestone: --- Created attachment 13919 --> https://sourceware.org/bugzilla/attachment.cgi?id=13919&action=edit Source files and compiled binary Compile using Intel OneAPI ifort version 2021.4.0: ifort -g -c strip_string.for ifort -g -c test.for ifort -o test test.o strip_string.o $ gdb ./test (gdb) info functions All defined functions: File strip_string.for: 1: ../../binutils-gdb/gdb/gdbtypes.h:441: internal-error: LONGEST dynamic_prop::const_val() const: Assertion `m_kind == PROP_CONST' failed A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) $ ./gdb -v GNU gdb (GDB) 11.1.90.20220113-git Compiled from git source of 11.1 tree (commit 707055a26 with 2e1875503 cherry-picked on top). -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-01-20 19:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-20 19:56 emr-gnu at hev dot psu.edu [this message] 2022-01-23 23:40 ` [Bug fortran/28801] " tromey at sourceware dot org 2022-01-23 23:40 ` tromey at sourceware dot org 2022-01-27 12:33 ` aburgess at redhat dot com 2022-01-28 16:08 ` tromey at sourceware dot org 2022-02-02 14:48 ` aburgess at redhat dot com 2022-02-24 16:04 ` tromey at sourceware dot org 2022-02-24 21:38 ` cvs-commit at gcc dot gnu.org 2022-02-24 21:39 ` 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-28801-4717@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: linkBe 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).