public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/23336] [3.4/4.0/4.1 Regression] enum constants not visible to gdb Date: Thu, 11 Aug 2005 18:59:00 -0000 [thread overview] Message-ID: <20050811185917.23184.qmail@sourceware.org> (raw) In-Reply-To: <20050811183444.23336.tromey@gcc.gnu.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-11 18:59 ------- Confirmed, another -feliminate-unused-debug-types bug. a regression from 3.3.3. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 Keywords| |wrong-debug Known to fail| |3.4.0 4.0.0 4.1.0 Known to work| |3.3.3 Last reconfirmed|0000-00-00 00:00:00 |2005-08-11 18:59:16 date| | Summary|enum constants not visible |[3.4/4.0/4.1 Regression] |to gdb |enum constants not visible | |to gdb Target Milestone|--- |4.0.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23336
next prev parent reply other threads:[~2005-08-11 18:59 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-11 18:34 [Bug debug/23336] New: " tromey at gcc dot gnu dot org 2005-08-11 18:59 ` pinskia at gcc dot gnu dot org [this message] 2005-09-27 15:58 ` [Bug debug/23336] [3.4/4.0/4.1 Regression] " mmitchel 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=20050811185917.23184.qmail@sourceware.org \ --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).