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 symtab/30827] New: [gdb/symtab, dwarf4-gdb-index] FAIL: gdb.ada/same_enum.exp: print red
Date: Wed, 06 Sep 2023 15:23:04 +0000	[thread overview]
Message-ID: <bug-30827-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30827

            Bug ID: 30827
           Summary: [gdb/symtab, dwarf4-gdb-index] FAIL:
                    gdb.ada/same_enum.exp: print red
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With test-case gdb.ada/same_enum.exp and target board dwarf4-gdb-index we run
into:
...
(gdb) print red^M
No definition of "red" in current context.^M
(gdb) FAIL: gdb.ada/same_enum.exp: print red
...

Minimal reproducer:
...
$ gdb -q -batch outputs/gdb.ada/same_enum/a -ex "print red"
No definition of "red" in current context.
...

After adding -readnow, it passes:
...
$ gdb -readnow -q -batch outputs/gdb.ada/same_enum/a -ex "print red"
$1 = red
...
so this looks like an index-related problem.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-09-06 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 15:23 vries at gcc dot gnu.org [this message]
2023-09-07  6:57 ` [Bug symtab/30827] " vries at gcc dot gnu.org
2023-09-07  7:24 ` vries at gcc dot gnu.org
2023-09-07 15:09 ` vries at gcc dot gnu.org
2023-09-07 19:59 ` cvs-commit at gcc dot gnu.org
2023-09-07 20:00 ` 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-30827-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: 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).