From: Daniel Jacobowitz <drow@false.org>
To: Peter Wainwright <peter.wainwright@ieee.org>
Cc: gdb@sourceware.org
Subject: Re: Cannot see local variables in C++ constructors
Date: Fri, 20 Feb 2009 18:06:00 -0000 [thread overview]
Message-ID: <20090220180629.GA8606@caradoc.them.org> (raw)
In-Reply-To: <1235152815.8484.4.camel@ceiriog.eclipse.co.uk>
On Fri, Feb 20, 2009 at 06:00:15PM +0000, Peter Wainwright wrote:
> I'm using gdb 6.8 with C++ code compiled by g++ 4.2.4 on Ubuntu 8.04.
>
> I cannot print the value of local variables inside constructors (e.g. I
> get 'No symbol "wire" in current context'). The code is compiled with
> -g and NO optimization.
>
> This symptom seems similar to
> http://sourceware.org/bugzilla/show_bug.cgi?id=8246
>
> But that's a really ancient bug (2003!): has anyone else seen this kind
> of trouble recently?
It's probably http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27574
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-02-20 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 18:00 Peter Wainwright
2009-02-20 18:06 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090220180629.GA8606@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=peter.wainwright@ieee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox