public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "aburgess at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug fortran/28801] "gdb/gdbtypes.h:441: internal-error: LONGEST dynamic_prop::const_val() const: Assertion `m_kind == PROP_CONST' failed" when listing functions Date: Thu, 27 Jan 2022 12:33:50 +0000 [thread overview] Message-ID: <bug-28801-4717-mMbcR9uGBe@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28801-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28801 Andrew Burgess <aburgess at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aburgess at redhat dot com --- Comment #3 from Andrew Burgess <aburgess at redhat dot com> --- Tom, I think that patch should go in. It may not give the user the answer they want, but given we immediately call the const_val method, I think checking only for the UNDEFINED case seems a bad idea. Just my thoughts... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-27 12:33 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-20 19:56 [Bug gdb/28801] New: " emr-gnu at hev dot psu.edu 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 [this message] 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-mMbcR9uGBe@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).