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 ada/29335] New: [gdb/ada, debug-types] FAIL: gdb.ada/local-enum.exp: print v1 element Date: Fri, 08 Jul 2022 08:00:39 +0000 [thread overview] Message-ID: <bug-29335-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29335 Bug ID: 29335 Summary: [gdb/ada, debug-types] FAIL: gdb.ada/local-enum.exp: print v1 element Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: ada Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- With test-case gdb.ada/local-enum.exp and target board debug-types, I run into: ... (gdb) print v1(three)^M No name 'three' in enumeration type 'local__e1'^M (gdb) FAIL: gdb.ada/local-enum.exp: print v1 element print v2(three)^M No name 'three' in enumeration type 'local__e2'^M (gdb) FAIL: gdb.ada/local-enum.exp: print v2 element ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-07-08 8:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-08 8:00 vries at gcc dot gnu.org [this message] 2023-04-19 18:24 ` [Bug ada/29335] " tromey at sourceware dot org 2023-04-20 8:03 ` vries at gcc dot gnu.org 2023-04-20 8:57 ` vries at gcc dot gnu.org 2023-04-27 16:30 ` tromey at sourceware dot org 2023-09-07 10:27 ` vries at gcc dot gnu.org 2023-09-07 15:10 ` vries at gcc dot gnu.org 2023-09-07 19:53 ` cvs-commit at gcc dot gnu.org 2023-09-07 19:54 ` vries at gcc dot gnu.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-29335-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).