Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: "Dmitry.Neverov via Gdb" <gdb@sourceware.org>
Cc: "Dmitry.Neverov" <dmitry.neverov@jetbrains.com>
Subject: Re: <incomplete type> in python api
Date: Wed, 26 Jun 2024 11:18:27 -0600	[thread overview]
Message-ID: <87wmmbsjvg.fsf@tromey.com> (raw)
In-Reply-To: <87wmnjguao.fsf@lubuntu2.mail-host-address-is-not-set> (Dmitry Neverov via Gdb's message of "Fri, 24 May 2024 16:26:39 +0200")

>>>>> "Dmitry" == Dmitry Neverov via Gdb <gdb@sourceware.org> writes:

Dmitry> When debug info is missing, -mi-var-create returns the '<incomplete type>' value:
Dmitry>   41-mi-var-create var1_buf * \"buf\""
Dmitry>   41^done,name="var1_buf",numchild="0",value="<incomplete type>",type="std::stringbuf",thread-id="1",displayhint="string",dynamic="1",has_more="0"

Dmitry> Debugger users can google for '<incomplete type>' and find possible ways
Dmitry> to address the problem.

Dmitry> Is it possible to detect such an incomplete type in python api?

Not really.  type::is_stub could probably be exposed to Python though.

Tom

      reply	other threads:[~2024-06-26 17:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 14:26 Dmitry.Neverov via Gdb
2024-06-26 17:18 ` Tom Tromey [this message]

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=87wmmbsjvg.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=dmitry.neverov@jetbrains.com \
    --cc=gdb@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