public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/44668] New: class->DW_TAG_typedef is missing DW_AT_accessibility Date: Fri, 25 Jun 2010 16:22:00 -0000 [thread overview] Message-ID: <bug-44668-12292@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1411 bytes --] echo 'class C { protected: typedef int t; t v; } c;' | g++ -Wall -c -g -x c++ - <2><33>: Abbrev Number: 3 (DW_TAG_typedef) <34> DW_AT_name : t <38> DW_AT_type : <0x4a> <2><3c>: Abbrev Number: 4 (DW_TAG_member) <3d> DW_AT_name : v <41> DW_AT_type : <0x33> <45> DW_AT_data_member_location: 2 byte block: 23 0 (DW_OP_plus_uconst: 0) <48> DW_AT_accessibility: 2 (protected) DIE <0x33> should have DW_AT_accessibility. FAIL g++ (GCC) 4.6.0 20100625 (experimental) FAIL g++ (GCC) 4.5.1 20100625 (prerelease) SKIP g++ (GCC) 4.4.5 20100625 (prerelease) - C::t is missing there. FAIL gcc-c++-4.4.4-8.fc14.x86_64 G++ properly respects the access control: .C:3: error: âtypedef int C::tâ is protected .C:11: error: within this context But GDB cannot display the access control during `ptype C'. GDB does not and probably should not respect the access control, though. -- Summary: class->DW_TAG_typedef is missing DW_AT_accessibility Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: minor Priority: P3 Component: debug AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jan dot kratochvil at redhat dot com GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44668
next reply other threads:[~2010-06-25 16:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-25 16:22 jan dot kratochvil at redhat dot com [this message] 2010-06-25 16:32 ` [Bug debug/44668] " jan dot kratochvil at redhat dot com 2010-06-25 16:54 ` jakub at gcc dot gnu dot org 2010-06-25 18:23 ` jakub at gcc dot gnu dot org 2010-06-29 19:38 ` jakub at gcc dot gnu dot org 2010-07-27 8:48 ` jakub at gcc dot gnu 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-44668-12292@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).