public inbox for
help / color / mirror / Atom feed
From: "jens.elmenthaler at me dot com" <>
Subject: [Bug mi/14030] New: No children returned for unitialized pointer to class
Date: Sat, 28 Apr 2012 07:36:00 -0000	[thread overview]
Message-ID: <> (raw)

             Bug #: 14030
           Summary: No children returned for unitialized pointer to class
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mi
    Classification: Unclassified

I have the following set of source/header files:

// ClassUnderTest.hpp
class ClassUnderTest  {

    virtual ~ClassUnderTest();

    bool mTrue;
    int mFifteen;

// ClassUnderTest.cpp
#include "ClassUnderTest.hpp"

: mTrue(true),


// client.cpp
void client()
  ClassUnderTest *pCUT= new ClassUnderTest;  // breakpoint here -> 0 children,
stepping to next line does not help
  delete pCUT;                               // breakpoint here -> OK
  pCUT = 0;

If I set a breakpoint at the first line in client(), pCUT has no children, and
also stepping over this line will not yield the children.

If I set the breakpoint to the second line, i.e. pCUT is initialized already, I
get the expected children.

It seems to be relevant that client() and the implementation of
ClassUnderTest's methods are in separate source files. If I implement the
methods in ClassUnderTest.hpp, or move client() into ClassUnderTest.cpp,
everything works properly again.

I use a gcc 4.1.2.

This seems to be related to the changes for bug 376901, which now rely on the
type information of the value instead of target type information calculated on
the fly (get_target_type()).

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

             reply	other threads:[~2012-04-28  7:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-28  7:36 jens.elmenthaler at me dot com [this message]
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
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).