public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/17762] template lookup: partial syms vs syms differences
Date: Fri, 21 Oct 2022 17:19:33 +0000	[thread overview]
Message-ID: <bug-17762-4717-IF6DTcjrIZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17762-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
This still seems to happen with the new reader.

The DWARF says:

    <2b>   DW_AT_name        : (indirect string, offset: 0x52):
thetemplatefunction<'\001'>

There isn't a way to dump the cooked index directly (probably
should fix) but you can gdb-add-index and examine that:

[710] thetemplatefunction<(char)'\001'>: 0 [global, function]

However info func says:

2:      int thetemplatefunction<(char)1>();


I'm going to say the bug is somewhere in the full reader.
This is a case that would be fixed by the lazy expansion
idea, see bug #29398 -- there, the names would be directly
constructed from the cooked index, so there's no possibility
of divergence.

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

  parent reply	other threads:[~2022-10-21 17:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-27  7:10 [Bug symtab/17762] New: " dje at google dot com
2014-12-27  7:35 ` [Bug symtab/17762] " dje at google dot com
2022-10-21 17:19 ` tromey at sourceware dot org [this message]
2022-10-21 17:20 ` tromey at sourceware dot org
2022-10-21 17:37 ` tromey at sourceware dot org
2022-10-21 17:43 ` tromey at sourceware dot org
2023-01-11 23:47 ` dblaikie at gmail dot com
2023-02-25  1:55 ` 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-17762-4717-IF6DTcjrIZ@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).