From: Graham Swallow <Information-Cascade@ntlworld.com>
To: insight@sources.redhat.com
Subject: Local Vars show prototype not structure
Date: Sat, 12 Oct 2002 08:41:00 -0000 [thread overview]
Message-ID: <20021012164120.795635a7.Information-Cascade@ntlworld.com> (raw)
Hi,
for several weeks I've been getting stubs in Local Variables.
(Possibly since I've increased use of incomplete declarations)
IE: It displays var_name (class str2 *) 0x819df40
when I'd hoped to see [+] and access to the objects fields.
I cant find a specific pattern of when I do/dont get the
tree, except that it is consistently stable, and sometimes
has const which I dont always expect. I tried some trivial
examples, but they all resolved fully.
The console p *this always works, except that it's three
miles long on one line. The active code has access to
the member fields, so the class has been fully declared.
The current window is even displaying 'this' as a stub,
for a member function.
Any ideas?
--
regards
--
Graham
Information-Cascade@ntlworld..c.o.m
next reply other threads:[~2002-10-12 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 8:41 Graham Swallow [this message]
2002-10-14 8:49 ` Keith Seitz
2002-10-14 11:03 ` Graham Swallow
2002-10-14 11:07 ` Keith Seitz
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=20021012164120.795635a7.Information-Cascade@ntlworld.com \
--to=information-cascade@ntlworld.com \
--cc=insight@sources.redhat.com \
/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).