public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug dap/30821] DAP GDB: "this" have no children. It comes with "variablesReference" 0.
Date: Tue, 05 Sep 2023 15:18:30 +0000	[thread overview]
Message-ID: <bug-30821-4717-ZvAQ2TPlTq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30821-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30821

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
I have a patch for this but it should probably wait for this series:

https://sourceware.org/pipermail/gdb-patches/2023-August/201771.html

My current patch regresses gdb.dap/scopes.exp, because it expects
the 'char *' variable not to have structure.
I'm not totally sure if the above series handles that well, but
it seems like it would be necessary infrastructure for it at least.

Hmm, it's been 2 weeks, perhaps I'll put that in.

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

  parent reply	other threads:[~2023-09-05 15:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04  8:34 [Bug dap/30821] New: " artem.sokolovskii at qt dot io
2023-09-04  8:36 ` [Bug dap/30821] DAP GDB: " artem.sokolovskii at qt dot io
2023-09-04 17:58 ` tromey at sourceware dot org
2023-09-05 13:11 ` tromey at sourceware dot org
2023-09-05 13:53 ` artem.sokolovskii at qt dot io
2023-09-05 15:18 ` tromey at sourceware dot org [this message]
2023-09-05 19:47 ` tromey at sourceware dot org
2023-09-06  8:52 ` artem.sokolovskii at qt dot io
2023-09-07 14:46 ` tromey at sourceware dot org
2023-09-19 19:34 ` cvs-commit at gcc dot gnu.org
2023-09-19 19:34 ` tromey at sourceware dot org
2023-09-20  9:25 ` artem.sokolovskii at qt dot io

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-30821-4717-ZvAQ2TPlTq@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).