This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: breakpoints at bogus locations

From: Allen Hopkins <allenh at eecs dot berkeley dot edu>
To: Florian Weimer <fw at deneb dot enyo dot de>
Cc: gcc-help at gcc dot gnu dot org
Date: Mon, 31 Jan 2005 14:28:22 -0800
Subject: Re: breakpoints at bogus locations
References: <41FE9251.3020100@eecs.berkeley.edu> <87mzuppc2y.fsf@deneb.enyo.de>

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?

References:
- breakpoints at bogus locations
  - From: Allen Hopkins
- Re: breakpoints at bogus locations
  - From: Florian Weimer

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]