From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6119 invoked by alias); 9 Jun 2003 14:16:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 5926 invoked by uid 48); 9 Jun 2003 14:15:57 -0000 Date: Mon, 09 Jun 2003 14:16:00 -0000 From: "drkent@lanl.gov" To: gcc-bugs@gcc.gnu.org Message-ID: <20030609141556.11134.drkent@lanl.gov> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/11134] New: DWARF Problems with const int globals X-Bugzilla-Reason: CC X-SW-Source: 2003-06/txt/msg01136.txt.bz2 List-Id: 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.