Re: c++/4966: g++ generates incorrect debugging information

Re: c++/4966: g++ generates incorrect debugging information

[bangerth]

Synopsis: g++ generates incorrect debugging information

State-Changed-From-To: feedback->open
State-Changed-By: bangerth
State-Changed-When: Sat Dec 21 11:03:21 2002
State-Changed-Why:
    Feedback received a long time ago already.
    
    Do you know whether this still happens with gcc3.2.1?
    
    Thanks
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4966

Re: c++/4966: g++ generates incorrect debugging information

[Matthias Meixner]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]

The following reply was made to PR c++/4966; it has been noted by GNATS.

From: Matthias Meixner <meixner@dvs1.informatik.tu-darmstadt.de>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   meixner@rbg.informatik.tu-darmstadt.de, nobody@gcc.gnu.org,
   rodrigc@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/4966: g++ generates incorrect debugging information
Date: Mon, 06 Jan 2003 09:32:34 +0100

 bangerth@dealii.org wrote:
 > Synopsis: g++ generates incorrect debugging information
 > 
 > State-Changed-From-To: feedback->open
 > State-Changed-By: bangerth
 > State-Changed-When: Sat Dec 21 11:03:21 2002
 > State-Changed-Why:
 >     Feedback received a long time ago already.
 >     
 >     Do you know whether this still happens with gcc3.2.1?
 
 I have just tested this with gcc3.2 and this error also happens with this 
 version, however I have not testest gcc3.2.1 yet, since I do not already have it.
 
 Regards,
 
 	Matthias Meixner
 
 -- 
 Matthias Meixner                       meixner@informatik.tu-darmstadt.de
 Technische Universität Darmstadt
 Datenbanken und Verteilte Systeme              Telefon (+49) 6151 16 6232
 Wilhelminenstraße 7, D-64283 Darmstadt, Germany    Fax (+49) 6151 16 6229
 

Re: c++/4966: g++ generates incorrect debugging information

[Matthias Meixner]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

The following reply was made to PR c++/4966; it has been noted by GNATS.

From: Matthias Meixner <meixner@rbg.informatik.tu-darmstadt.de>
To: rodrigc@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        nobody@gcc.gnu.org
Subject: Re: c++/4966: g++ generates incorrect debugging information
Date: Fri, 30 Nov 2001 12:30:00 +0100

 rodrigc@gcc.gnu.org wrote:
 > 
 > Synopsis: g++ generates incorrect debugging information
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: rodrigc
 > State-Changed-When: Thu Nov 29 13:53:00 2001
 > State-Changed-Why:
 >     What version of gdb are you using?  The latest
 >     gdb version has better support for gcc 3.0.2,
 >     for things such as the new name mangling format in
 >     gcc 3.0.x.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4966&database=gcc
 
 I tested it using gdb 4.18, 5.0 and I think 5.1, all show the same behaviour.
 
 Regards,
 
 	Matthias Meixner
 
 -- 
 Matthias Meixner                   meixner@rbg.informatik.tu-darmstadt.de
 Technische Universität Darmstadt
 Rechnerbetriebsgruppe                          Telefon (+49) 6151 16 6670
 Alexanderstraße 6, D-64283 Darmstadt, Germany      Fax (+49) 6151 16 4701

Re: c++/4966: g++ generates incorrect debugging information

[rodrigc]

The following reply was made to PR c++/4966; it has been noted by GNATS.

From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  meixner@rbg.informatik.tu-darmstadt.de, nobody@gcc.gnu.org,
  rodrigc@gcc.gnu.org
Cc:  
Subject: Re: c++/4966: g++ generates incorrect debugging information
Date: 29 Nov 2001 21:53:00 -0000

 Synopsis: g++ generates incorrect debugging information
 
 State-Changed-From-To: open->feedback
 State-Changed-By: rodrigc
 State-Changed-When: Thu Nov 29 13:53:00 2001
 State-Changed-Why:
     What version of gdb are you using?  The latest
     gdb version has better support for gcc 3.0.2,
     for things such as the new name mangling format in
     gcc 3.0.x.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4966&database=gcc

Re: c++/4966: g++ generates incorrect debugging information

[rodrigc]

Synopsis: g++ generates incorrect debugging information

State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Thu Nov 29 13:53:00 2001
State-Changed-Why:
    What version of gdb are you using?  The latest
    gdb version has better support for gcc 3.0.2,
    for things such as the new name mangling format in
    gcc 3.0.x.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4966&database=gcc

c++/4966: g++ generates incorrect debugging information

[meixner]

>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