This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
c++/4966: g++ generates incorrect debugging information
- From: meixner at rbg dot informatik dot tu-darmstadt dot de
- To: gcc-gnats at gcc dot gnu dot org
- Date: 29 Nov 2001 10:49:40 -0000
- Subject: c++/4966: g++ generates incorrect debugging information
- Reply-to: meixner at rbg dot informatik dot tu-darmstadt dot de
[Get raw message]
>Number: 4966
>Category: c++
>Synopsis: g++ generates incorrect debugging information
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Nov 29 02:56:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Matthias Meixner
>Release: gcc version 3.0.2
>Organization:
>Environment:
Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.0.2/specs
Configured with: ../configure --prefix=/usr/local --enable-languages=c,c++ --enable-threads=posix --disable-shared
Thread model: posix
gcc version 3.0.2
Suse-Linux 7.2
>Description:
g++ generates incorrect debugging information to be used by gdb
>How-To-Repeat:
compile:
g++ -g foo.cxx
debug
gdb a.out
break 21 ## Note: this should be the line a=a_;
run
####
The breakpoint is not hit, although the program passes this
point, which you can see, when single-stepping through the
program.
This does not happen, when using g++ version 2.95.2, so I
think gcc is generating wrong debugging information
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="foo.cxx"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="foo.cxx"
CmNsYXNzIEEgewogIGludCB4OwpwdWJsaWM6CiAgIEEoKTsKfTsKCkE6OkEoKSB7CiAgIHg9MTsg
Cn0gIAoKCmNsYXNzIEIgewogICBpbnQgYSxiOwpwdWJsaWM6CiAgIEIoaW50IGFfLGludCBiXyk7
Cn07CgpCOjpCKGludCBhXyxpbnQgYl8pIAp7CiAgIGE9YV87CiAgIGI9Yl87Cn0KCm1haW4oKQp7
CiAgIEIoMSwyKTsKfQoK