public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jens.elmenthaler at me dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/14030] No children returned for unitialized pointer to class
Date: Sat, 28 Apr 2012 10:15:00 -0000 [thread overview]
Message-ID: <bug-14030-4717-hxCabxsqQp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14030-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14030
--- Comment #2 from Jens Elmenthaler <jens.elmenthaler at me dot com> 2012-04-28 10:14:27 UTC ---
(In reply to comment #1)
> Probably you meant gdb bug 13393, cause the 376901 one is for Eclipse CDT.
> And I have one more question: is the problem reproducible with "set print
> object" on or off?
Oh, yes I meant 13393.
The problem occurs only with "set print object on". The call tree of interest
is:
mi_cmd_var_create
-> print_varobj
-> varobj_get_num_children
-> cplus_number_of_children
-> adjust_value_for_child_access
if on: it uses the target type in value, which has not set nfields yet
if off: it uses get_target_type() from the type parameter, which then
also resolves the nfields parameter.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-04-28 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 7:36 [Bug mi/14030] New: " jens.elmenthaler at me dot com
2012-04-28 7:38 ` [Bug mi/14030] " jens.elmenthaler at me dot com
2012-04-28 8:11 ` xgsa at yandex dot ru
2012-04-28 10:15 ` jens.elmenthaler at me dot com [this message]
2012-05-12 16:51 ` xgsa at yandex dot ru
2023-08-31 17:18 ` [Bug varobj/14030] " tromey at sourceware dot org
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=bug-14030-4717-hxCabxsqQp@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).