This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: problems debugging gcc
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>