public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/17004] print base::operator char * passes in cpexprs.exp, but only accidentally Date: Mon, 02 Jun 2014 18:56:00 -0000 [thread overview] Message-ID: <bug-17004-4717-rNoICd2KJK@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17004-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17004 --- Comment #3 from dje at google dot com --- The attached example shows gdb not able to find operator char *, due to it being looked up as operatorchar *. The key is to not cause the symtab with the operator definition to be prematurely expanded, forcing gdb to try to look up the operator in .gdb_index. The attached example puts main in one .o, the class definition in the next, and the operator definition in the last. (gdb) p base::operator char* There is no field named operatorchar * -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2014-06-02 18:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-30 23:18 [Bug c++/17004] New: " dje at google dot com 2014-05-31 1:03 ` [Bug c++/17004] " dje at google dot com 2014-06-02 18:53 ` dje at google dot com 2014-06-02 18:56 ` dje at google dot com [this message]
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-17004-4717-rNoICd2KJK@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).