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/30720] New: [gdb/symtab, gdb-index] FAIL: gdb.python/py-symbol.exp: print (len (gdb.lookup_static_symbols ('rr'))) Date: Fri, 04 Aug 2023 14:26:23 +0000 [thread overview] Message-ID: <bug-30720-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30720 Bug ID: 30720 Summary: [gdb/symtab, gdb-index] FAIL: gdb.python/py-symbol.exp: print (len (gdb.lookup_static_symbols ('rr'))) 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.python/py-symbol.exp and target board cc-with-gdb-index, I run into: ... (gdb) python print (len (gdb.lookup_static_symbols ('rr')))^M 1^M (gdb) FAIL: gdb.python/py-symbol.exp: print (len (gdb.lookup_static_symbols ('rr'))) ... This is especially confusing when you're using the index-cache. $ rm -Rf ~/.cache/gdb/* $ gdb -q -batch -iex "set index-cache enabled on" py-symbol \ -ex "python print (len (gdb.lookup_static_symbols ('rr')))" 2 $ gdb -q -batch -iex "set index-cache enabled on" py-symbol \ -ex "python print (len (gdb.lookup_static_symbols ('rr')))" 1 ... This is a regression, this passes in gdb-12-branch. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-08-04 14:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-04 14:26 vries at gcc dot gnu.org [this message] 2023-08-04 17:36 ` [Bug symtab/30720] " vries at gcc dot gnu.org 2023-08-13 12:08 ` cvs-commit at gcc dot gnu.org 2023-08-13 12:08 ` 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-30720-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).