public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drkent@lanl.gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11134] New: DWARF Problems with const int globals
Date: Mon, 09 Jun 2003 14:16:00 -0000	[thread overview]
Message-ID: <20030609141556.11134.drkent@lanl.gov> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11134

           Summary: DWARF Problems with const int globals
           Product: gcc
           Version: 3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: drkent@lanl.gov
                CC: gcc-bugs@gcc.gnu.org

I am developing a dynamic instrumentation tool that uses DWARF and have
encountered a few problems that could be from the dwarf information generated by
g++  3.3.

There are a few global variables defined as "const int".  When the tool parses
the binary, it attempts to locate these variables and then gives a
DW_DLV_NO_ENTRY error which means that the attribute is not where the dwarf
information says it is.

I have avoided these problems by changing the global const ints to #define
statments, and the code runs properly.

Please contact me with any questions.


             reply	other threads:[~2003-06-09 14:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 14:16 drkent@lanl.gov [this message]
2003-06-09 14:21 ` [Bug c++/11134] " drow@mvista.com
2003-06-09 14:29 ` dberlin@dberlin.org
2003-06-09 14:38 ` drow@mvista.com
2003-06-09 18:32 ` drkent@lanl.gov
2003-06-09 18:33 ` [Bug c++/11134] DWARF-2/3 " pinskia@physics.uc.edu
2003-06-09 18:33 ` [Bug c++/11134] DWARF " drkent@lanl.gov
2003-06-18 14:57 ` [Bug c++/11134] DWARF-2/3 " drkent at lanl dot gov
2003-06-28 18:27 ` pinskia at physics dot uc dot edu
2003-11-21 15:49 ` [Bug debug/11134] " pinskia at gcc dot gnu dot org
2004-01-17 23:37 ` dhazeghi at yahoo dot com
2004-01-20 14:09 ` drkent at lanl dot gov
2004-01-20 16:18 ` dhazeghi at yahoo dot com
2004-01-23 20:15 ` drow 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=20030609141556.11134.drkent@lanl.gov \
    --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).