public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dje@watson.ibm.com
To: gcc-gnats@gcc.gnu.org
Subject: debug/3202: incorrect debugging line number and/or file
Date: Fri, 15 Jun 2001 23:16:00 -0000	[thread overview]
Message-ID: <20010616061220.8160.qmail@sourceware.cygnus.com> (raw)

>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:


             reply	other threads:[~2001-06-15 23:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15 23:16 dje [this message]
2001-06-19 11:38 dje

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010616061220.8160.qmail@sourceware.cygnus.com \
    --to=dje@watson.ibm.com \
    --cc=gcc-gnats@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).