This is the mail archive of the gcc-bugs@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: g++ 3.2.1 not generating proper debugging information

From: Jim Wilson <wilson at specifixinc dot com>
To: S B <mailsb04-posts at yahoo dot com>
Cc: gcc-bugs at gcc dot gnu dot org
Date: Thu, 04 Mar 2004 13:42:26 -0800
Subject: Re: g++ 3.2.1 not generating proper debugging information
References: <20040304005234.95061.qmail@web80402.mail.yahoo.com>

S B wrote:

When I compile this with -g and default optimization and load it in
gdb, I can't see all the local variables via 'info locals'.

The locals are there, but they have been put into a lexical block, which is not correct. The current development sources seem to handle this correctly. a, b, and c are visible in the entire function except the prologue/epilogue, and k is visible only after the loop.

info locals still didn't work for me though. It fails to print the value of a, and then bails out.

This is for an x86-linux target that uses dwarf2 debug info. I didn't check a stabs target like solaris.

By the way, we do not track bug reports sent to the mailing lists. We only track bug reports filed into our bugzilla database. If you want action taken on a bug report, it is better to put it in buzilla than to mail it to gcc-bugs. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

References:
- g++ 3.2.1 not generating proper debugging information
  - From: S B

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