This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: breakpoints at bogus locations
- From: lrtaylor at micron dot com
- To: <allenh at eecs dot berkeley dot edu>, <fw at deneb dot enyo dot de>
- Cc: <gcc-help at gcc dot gnu dot org>
- Date: Mon, 31 Jan 2005 15:39:03 -0700
- Subject: RE: breakpoints at bogus locations
Have you tried just using '-g' instead of '-ggdb'?
Thanks,
Lyle
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of Allen Hopkins
Sent: Monday, January 31, 2005 3:28 PM
To: Florian Weimer
Cc: gcc-help@gcc.gnu.org
Subject: Re: breakpoints at bogus locations
I'm using "-ggdb" and no "-O" option, but I've also tried adding "-O0",
with no change. I haven't tried it with optimization turned on, but is
there any point in that? I just seems like that would lead to more
confusion, not less. But any ideas of things to try are welcome, if it
might shed light on the problem.
-Allen
Florian Weimer wrote:
> * Allen Hopkins:
>
>
>>I've run "readelf -wl" to look at the DWARF-2 correspondence between
>>line numbers and addresses. The address corresponding to the line in
>>question is also associated with lines in other source files. So
>>something looks screwy with g++.
>
>
> Do you observe this behavior with -O0, or with optimization turned on?