public inbox for
help / color / mirror / Atom feed
From: "xgsa at yandex dot ru" <>
Subject: [Bug mi/14030] No children returned for unitialized pointer to class
Date: Sat, 12 May 2012 16:51:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #3 from Anton <xgsa at yandex dot ru> 2012-05-12 16:50:59 UTC ---
Unfortunately I cannot reproduce the problem with gdb HEAD and gcc-4.6.3. I see
the children even if I set the breakpoint on pCUT declaration (certainly they
have random values before initialization).  I still have children after pCUT is
initialized and even after "0" assignment.

I am not sure, but it could be a gcc-specific behavior. Could you try a newer

Otherwise we could try to reproduce the problem without relying on
uninitialized variable (which could give us random effect). E.g. is the problem
is reproducible in your environment if client() will looks like this:

void client()
  ClassUnderTest *pCUT = 0;   // Initialize variable to avoid random effect
  pCUT = new ClassUnderTest;  // breakpoint here -> 0 children,
stepping to next line does not help
  delete pCUT;                               // breakpoint here -> OK
  pCUT = 0;

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2012-05-12 16:51 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
2012-05-12 16:51 ` xgsa at yandex dot ru [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).