Re: debug/3202: incorrect debugging line number and/or file

Re: debug/3202: incorrect debugging line number and/or file

[dje]

Synopsis: incorrect debugging line number and/or file

State-Changed-From-To: open->closed
State-Changed-By: dje
State-Changed-When: Tue Jun 19 11:38:21 2001
State-Changed-Why:
    assembler bug

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3202&database=gcc

debug/3202: incorrect debugging line number and/or file

[dje]

>Number:         3202
>Category:       debug
>Synopsis:       incorrect debugging line number and/or file
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jun 15 23:16:02 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     dje@watson.ibm.com
>Release:        gcc 3.0 20010614 (prerelease)
>Organization:
>Environment:
powerpc-ibm-aix4.3.3.0
>Description:
C source code which includes files defining functions,
especially functions which refer back to the first file,
produce debugging information which refers to the wrong
filename and/or the wrong line number in the file.

This likely affects all dbxout ports, not just AIX xcoffout.
>How-To-Repeat:
Debug an application which throws an exception through
libgcc_s.sh unwind-dw2.c, which includes unwind.inc, and
step through the functions.  GDB complains about line
numbers greater than the number of lines in the files and
jumps to source code which is not related to the function
being debugged, but is a correct line number in another file.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: