public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jcownie at etnus dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/16063] New: Debuggers need more information about enum types in C++ Date: Fri, 18 Jun 2004 16:13:00 -0000 [thread overview] Message-ID: <20040618161255.16063.jcownie@etnus.com> (raw) The debug information emitted for enumerated types does not allow a debugger to unambiguously determine the "underlying type" of the enumeration. A debugger therefore does not have enough information to allow it to perform overload resolution when asked to evaluate a function call with an enum type as an actual argument. One can view this either as a bug (the compiler is emitting an unsigned value using DW_FORM_sdata), or as requiring an enhancement. I believe the simplest solution would be to have the compiler be explicit about the representation of the enum type by emitting a DW_AT_encoding with the DW_TAG_enumeration, so that the debugger is explicitly told whether the underlying type of the enumeration is signed or unsigned. See the (about to be attached) test case for detailed information. -- Summary: Debuggers need more information about enum types in C++ Product: gcc Version: 3.4.0 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: debug AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jcownie at etnus dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16063
next reply other threads:[~2004-06-18 16:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-18 16:13 jcownie at etnus dot com [this message] 2004-06-18 16:14 ` [Bug debug/16063] " jcownie at etnus dot com 2004-06-18 16:22 ` pinskia at gcc dot gnu dot org 2004-06-18 16:31 ` jcownie at etnus 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=20040618161255.16063.jcownie@etnus.com \ --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).