From: Geoff Keating <geoffk@geoffk.org>
To: neil@daikokuya.demon.co.uk
Cc: gcc@gcc.gnu.org
Subject: Re: problems debugging gcc
Date: Tue, 04 Dec 2001 15:27:00 -0000 [thread overview]
Message-ID: <200112042325.PAA32650@geoffk.org> (raw)
In-Reply-To: <20011204223213.A23655@daikokuya.demon.co.uk> (message from Neil Booth on Tue, 4 Dec 2001 22:32:13 +0000)
> Date: Tue, 4 Dec 2001 22:32:13 +0000
> From: Neil Booth <neil@daikokuya.demon.co.uk>
> Cc: gcc@gcc.gnu.org
> Content-Disposition: inline
> User-Agent: Mutt/1.3.23i
>
> Geoff Keating wrote:-
>
> > There's a bug in cc1: it doesn't store file names for statements, only
> > line numbers, and so debugging information for functions that have
> > lines from multiple files is often wrong.
>
> Hmm, sounds like it's non-trivial to fix and been around forever then.
>
> It also sounds like a good reason to use the line maps and drop the
> mucking about with global filename and line number variables, no?
Oh, it's not related to the global variables. If it was just that,
I'd have fixed it a month ago. Look at STMT_LINENO in c-common.h, and
notice there is no STMT_FILENAME nor any easy way to add one.
It started around when functions-as-trees was added.
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>
next prev parent reply other threads:[~2001-12-04 23:27 UTC|newest]
Thread overview: 10+ 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
2001-12-04 14:24 ` Geoff Keating
2001-12-04 14:31 ` Neil Booth
2001-12-04 15:27 ` Geoff Keating [this message]
2001-12-04 15:37 ` Neil Booth
2001-12-05 15:43 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2001-12-04 1:21 Danish Samad
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=200112042325.PAA32650@geoffk.org \
--to=geoffk@geoffk.org \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@redhat.com \
--cc=neil@daikokuya.demon.co.uk \
/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).