public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dodji at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/39705] enum constants don't appear in debug_pubnames
Date: Wed, 29 Jul 2009 12:40:00 -0000 [thread overview]
Message-ID: <20090729124022.7872.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39705-360@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
------- Comment #1 from dodji at gcc dot gnu dot org 2009-07-29 12:40 -------
Subject: Re: New: enum constants don't appear in debug_pubnames
Le 10/04/2009 01:42, tromey at gcc dot gnu dot org a écrit :
> enum constants don't appear in .debug_pubnames.
> It seems like perhaps they should, because they are global (in a sense).
The attached patchlet seems to be doing the trick.
The entry in the .debug_pubname for a given enum constant points to the
corresponding DW_TAG_enumerator DIE representing the enum constant in the
.debug_info section.
Is this what you meant ?
------- Comment #2 from dodji at gcc dot gnu dot org 2009-07-29 12:40 -------
Created an attachment (id=18267)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18267&action=view)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39705
next prev parent reply other threads:[~2009-07-29 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 23:42 [Bug debug/39705] New: " tromey at gcc dot gnu dot org
2009-07-27 14:36 ` [Bug debug/39705] " dodji at gcc dot gnu dot org
2009-07-29 12:40 ` dodji at redhat dot com [this message]
2010-07-19 18:44 ` tromey 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=20090729124022.7872.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: 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).