This is the mail archive of the gcc-patches@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: Variable tracking (location lists support) - part 1

From: Daniel Berlin <dberlin at dberlin dot org>
To: "Joseph S. Myers" <jsm at polyomino dot org dot uk>
Cc: gcc-patches at gcc dot gnu dot org,Josef Zlomek <zlomj9am at artax dot karlin dot mff dot cuni dot cz>
Date: Thu, 29 Jan 2004 15:05:29 -0500
Subject: Re: Variable tracking (location lists support) - part 1
References: <20040129182612.GA9962@artax.karlin.mff.cuni.cz> <Pine.LNX.4.58.0401291957130.23288@digraph.polyomino.org.uk>

On Jan 29, 2004, at 2:59 PM, Joseph S. Myers wrote:

On Thu, 29 Jan 2004, Josef Zlomek wrote:

Without location lists, GDB printed some wierd values when debugging optimized code. GDB with support of location lists (GDB 6.0.1 and newer) shows correct values of variables even when debugging optimized code even with -fomit-frame-pointer (when !frame_pointer_needed a special location list for describing the changes of stack pointer is emitted).
Does this mean that some targets that didn't previously should now have
-fomit-frame-pointer enabled at -O?

They could, assuming they output dwarf2.

References:
- Variable tracking (location lists support) - part 1
  - From: Josef Zlomek
- Re: Variable tracking (location lists support) - part 1
  - From: Joseph S. Myers

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