From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: "info locals" -- is variable initialized
Date: Fri, 02 Sep 2005 13:13:00 -0000 [thread overview]
Message-ID: <20050902131321.GA12830@nevyn.them.org> (raw)
In-Reply-To: <df97f5$gmh$1@sea.gmane.org>
On Fri, Sep 02, 2005 at 01:53:41PM +0400, Vladimir Prus wrote:
> So, there's a window there variable does not exists according to C++, but
> exists according to gdb.
With better debug information, this doesn't happen (or the window is
reduced to an instruction or two in the call sequence for the
constructor). GCC 4's variable tracking feature does this passably
well, IIRC, by use of dwarf2 location lists.
In general no there is nothing gdb can do.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-02 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 7:58 Vladimir Prus
2005-09-02 9:28 ` Ramana Radhakrishnan
2005-09-02 9:57 ` Vladimir Prus
2005-09-02 13:13 ` Daniel Jacobowitz [this message]
2005-09-02 13:19 ` Vladimir Prus
2005-09-02 13:21 ` Daniel Jacobowitz
2005-09-02 13:28 ` Vladimir Prus
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=20050902131321.GA12830@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).