public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/12936] New: function lookup class should not depend on its linkage name
Date: Mon, 27 Jun 2011 15:03:00 -0000	[thread overview]
Message-ID: <bug-12936-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=12936

           Summary: function lookup class should not depend on its linkage
                    name
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned@sourceware.org
        ReportedBy: jan.kratochvil@redhat.com


struct S {
  static void m (int x) {}
};
template<void (*T) (int)>
struct K {
  void f () { T (0); }
};
int main () {
  K<&S::m> k;
  k.f ();
}
------------------------------------------------------------------------------
K<&S::m>::f (this=0x7fffffffdc9f) at tmplmembernot.C:6
6      void f () { T (0); }
(gdb) p T
No symbol "T" in current context.
(gdb) ptype T
No symbol "T" in current context.

expected:
(gdb) ptype T
type = void (int)
 - `print T' is another problem - GDB PR c++/12933

cp_lookup_symbol_imports_or_template uses namespaces from
`SYMBOL_NATURAL_NAME (function)' which may come demangled from
DW_AT_linkage_name and it may not match parent
DW_TAG_structure_type->DW_AT_name such as due to:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49546

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2011-06-27 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 15:03 jan.kratochvil at redhat dot com [this message]
2011-11-18 19:45 ` [Bug c++/12936] " tromey at redhat dot com

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-12936-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).