public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: gcc-gnats@gcc.gnu.org, mike stump <mrs@windriver.com>,
	danishsamad@yahoo.com, gcc@gcc.gnu.org
Subject: Re: [c/4053] Re: problems debugging gcc
Date: Tue, 04 Dec 2001 13:18:00 -0000	[thread overview]
Message-ID: <20011204211901.B22784@daikokuya.demon.co.uk> (raw)
In-Reply-To: <20011204160845.A15532@nevyn.them.org>

Daniel Jacobowitz wrote:-

> Well, it isn't in the debug format code; the file information in the
> RTL is wrong.  And there's nothing obviously incorrect about the code
> in cb_file_change...
> 
> Aha, I think I see it.  cb_file_change updates input_filename as it
> reads.  Compile the testcase from the PR with a breakpoint on
> cb_file_change and a breakpoint on emit_line_note.  If I had to guess,
> I'd say that the problem was input_filename describing the state of the
> lexer where it used to describe the state of the parser.  In
> c_expand_body is the line:
>   init_function_start (fndecl, input_filename, DECL_SOURCE_LINE (fndecl));
> 
> DECL_SOURCE_LINE is fine.  input_filename isn't.

Cool!  This looks like it.  I'll take a closer look and post a patch
if it works.

Thanks a lot for the detective work!

Neil.

  reply	other threads:[~2001-12-04 21:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 11:59 mike stump
2001-12-04 12:34 ` Neil Booth
2001-12-04 13:08   ` [c/4053] " Daniel Jacobowitz
2001-12-04 13:18     ` Neil Booth [this message]
2001-12-04 14:24   ` Geoff Keating
2001-12-04 14:31     ` Neil Booth
2001-12-04 15:27       ` Geoff Keating
2001-12-04 15:37         ` Neil Booth
2001-12-05 15:43           ` Richard Henderson
2001-12-04 17:03 [c/4053] " mike stump
2001-12-05 15:10 ` Neil Booth

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=20011204211901.B22784@daikokuya.demon.co.uk \
    --to=neil@daikokuya.demon.co.uk \
    --cc=danishsamad@yahoo.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mrs@windriver.com \
    /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).