public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/30720] [gdb/symtab, gdb-index] FAIL: gdb.python/py-symbol.exp: print (len (gdb.lookup_static_symbols ('rr')))
Date: Sun, 13 Aug 2023 12:08:20 +0000	[thread overview]
Message-ID: <bug-30720-4717-mW9bMTgsgB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30720-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=aef36dee93bf194cb0b976a4ae49a79a736a188d

commit aef36dee93bf194cb0b976a4ae49a79a736a188d
Author: Tom de Vries <tdevries@suse.de>
Date:   Sun Aug 13 14:08:06 2023 +0200

    [gdb/symtab] Don't deduplicate variables in gdb-index

    When running test-case gdb.python/py-symbol.exp with target board
    cc-with-gdb-index, we 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')))
    ...

    [ Note that the test-case contains rr in both py-symtab.c:
    ...
    static int __attribute__ ((used)) rr = 42;      /* line of rr */
    ...
    and py-symtab-2.c:
    ...
    static int __attribute__ ((used)) rr = 99;      /* line of other rr */
    ... ]

    This passes with gdb-12-branch, and fails with gdb-13-branch.

    AFAIU the current code in symtab_index_entry::minimize makes the assumption
    that it's fine to store only one copy of rr in the gdb-index, because
    "print rr" will only ever print one, and always the same.

    But that fails to recognize that gdb supports gdb.lookup_static_symbols,
which
    returns a list of variables rather than the first one.

    In other words, the current approach breaks feature parity between cooked
    index and gdb-index.

    Note btw that also debug-names has both instances:
    ...
    [  5] #00597969 rr:
            <4> DW_TAG_variable DW_IDX_compile_unit=3 DW_IDX_GNU_internal=1
            <4> DW_TAG_variable DW_IDX_compile_unit=4 DW_IDX_GNU_internal=1
    ...

    Fix this in symtab_index_entry::minimize, by not deduplicating variables.

    Tested on x86_64-linux, with target boards unix and cc-with-gdb-index.

    Reviewed-by: Kevin Buettner <kevinb@redhat.com>

    PR symtab/30720
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30720

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

  parent reply	other threads:[~2023-08-13 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 14:26 [Bug symtab/30720] New: " vries at gcc dot gnu.org
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 [this message]
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-mW9bMTgsgB@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).