public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH] Have DAP handle non-Value results from 'children'
Date: Mon, 16 Oct 2023 09:40:04 -0600	[thread overview]
Message-ID: <87r0lushij.fsf@tromey.com> (raw)
In-Reply-To: <20231006134413.2655181-1-tromey@adacore.com> (Tom Tromey via Gdb-patches's message of "Fri, 6 Oct 2023 07:44:13 -0600")

>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:

Tom> A pretty-printer's 'children' method may return values other than a
Tom> gdb.Value -- it may return any value that can be converted to a
Tom> gdb.Value.

Tom> I noticed that this case did not work for DAP.  This patch fixes the
Tom> problem.

I'm checking this one in as well.
I think this is the last pending DAP patch... there are a few in the
works but nothing too critical AFAIK.

Tom

      reply	other threads:[~2023-10-16 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06 13:44 Tom Tromey
2023-10-16 15:40 ` 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=87r0lushij.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@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).