public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: dan@debian.org To: gcc-gnats@gcc.gnu.org Subject: c/4053: Filenames in debug info for included files are incorrect Date: Fri, 17 Aug 2001 16:06:00 -0000 [thread overview] Message-ID: <20010817230002.30037.qmail@sourceware.cygnus.com> (raw) >Number: 4053 >Category: c >Synopsis: Filenames in debug info for included files are incorrect >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Aug 17 16:06:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: dan@debian.org >Release: gcc 3_0 branch >Organization: >Environment: i686-pc-linux-gnu native, or i686-pc-linux-gnu -> mips-unknown-linux-gnu cross. >Description: Take two files, linetest.h: a = b; c = d; e = f; and linetest.c: int main() { int a, b, c, d, e, f; a = b = c = d = e = f = 0; #include "linetest.h" return 0; } Compile with debugging. Notice that the filename is never changed - the three lines from the header have debug info indicating they are the first three lines of linetest.c. This is a regression from 2.95.x, but not from 3.0 release. It's independent of debug format - the line notes are wrong. I'd check HEAD, but it segfaults in _cpp_simplify_pathname because "/usr/local/include" is not writeable today. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-08-17 16:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-08-17 16:06 dan [this message] 2001-08-18 14:26 Daniel Jacobowitz 2001-11-01 13:42 neil 2001-11-01 13:56 neil 2002-04-25 23:25 rth
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=20010817230002.30037.qmail@sourceware.cygnus.com \ --to=dan@debian.org \ --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: linkBe 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).