This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/11098] New: g++ doesn't emit complete debugging information for local variables in destructors


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

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

           Summary: g++ doesn't emit complete debugging information for
                    local variables in destructors
           Product: gcc
           Version: 3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: mvanier@cs.caltech.edu
                CC: gcc-bugs@gcc.gnu.org

Consider this code (in the file "foo.cc"):

// Begin code:
class Test {
private:
    int *data;
public:
    Test();
    ~Test();
};

Test::Test() {
    data = new int[1000];
}

Test::~Test() {
    int *t = data;
    delete [] t;
}


int main() {
    Test s;
    return 0;
}
// End code.

When I compile this with "g++ -Wall -g foo.cc -o foo" and then bring up gdb 5.3
and set a breakpoint in the destructor, this happens:

[tap] gdb foo
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(gdb) break Test::~Test()
Breakpoint 1 at 0x80484c6: file foo.cc, line 13.
(gdb) run
Starting program: /home/mvanier/tmp/cs11/foo 

Breakpoint 1, ~Test (this=0xbfffee30) at foo.cc:14
14          int *t = data;
(gdb) p t
No symbol "t" in current context.
(gdb) info locals
No locals.
(gdb) 

Clearly this is wrong, as "t" is a local variable in the destructor.

I sent in a bug report to the gdb developers, and they say that the reason this
is happening is that g++ is not outputting the correct debugging information.
They tell me I should refer you to bugs debug/10156 in the gcc GNATS database
and c++/1234 in the gdb GNATS database (the latter being the one I submitted).
Thanks in advance for your help.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]