From: Geoff Keating <geoffk@geoffk.org>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: gcc@gcc.gnu.org
Subject: Re: problems debugging gcc
Date: Tue, 04 Dec 2001 14:24:00 -0000 [thread overview]
Message-ID: <jmwv02zksp.fsf@geoffk.org> (raw)
In-Reply-To: Neil Booth's message of "Tue, 4 Dec 2001 20:34:54 +0000"
Neil Booth <neil@daikokuya.demon.co.uk> writes:
> mike stump wrote:-
>
> > Yes. Step through bison.simple a couple hundred times, and you'll
> > discover that most of the time, it spends it's time in about two to
> > four places you care about. One place, is dispatching to actions. It
> > can be felt, by noticing the line (at least in bison 1.25):
>
> Have you noticed that you often get the debugger trying to step to a
> line in bison.simple that is in fact in parse.y, and complaining about
> a line out range?
>
> This happens to me very frequently; I have no idea what causes it. I
> have a sneaking suspicion that this GCC bug is what the original post
> was about, though I'm not sure.
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.
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>
next prev parent reply other threads:[~2001-12-04 22:24 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 [this message]
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
-- 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=jmwv02zksp.fsf@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).