public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/5] Handle pointers and references correctly in DAP
Date: Tue, 05 Sep 2023 13:47:00 -0600	[thread overview]
Message-ID: <20230905-dap-30821-pointers-v1-0-0d7323327678@adacore.com> (raw)

This series started off as a simple implementation of a no-op
pretty-printer to handle pointers and references in DAP.

However, this regressed a test, and I realized that the new
is-array-like and is-string-like code should be generalized to work
with any language.

This is done by associating a language with each type, which meant
touching every debug reader, plus a few minor preliminary cleanups.

Regression tested on x86-64 Fedora 36.

---
Tom Tromey (5):
      Pass a type allocator to init_fixed_point_type
      Regularize some DWARF type initialization
      Add is_array_like and to_array to language_defn
      Give a language to a type
      Handle pointers and references correctly in DAP

 gdb/ada-lang.c                   |  13 +++++
 gdb/coffread.c                   |   4 +-
 gdb/ctfread.c                    |  17 ++++---
 gdb/dwarf2/read.c                |  89 +++++++++++++++++----------------
 gdb/gdbtypes.c                   |  31 ++++++------
 gdb/gdbtypes.h                   |  37 ++++++++------
 gdb/language.h                   |  11 +++++
 gdb/mdebugread.c                 |   9 ++--
 gdb/python/lib/gdb/printing.py   |  16 ++++++
 gdb/python/py-type.c             |  13 ++---
 gdb/rust-lang.h                  |  10 ++++
 gdb/stabsread.c                  |  20 ++++----
 gdb/testsuite/gdb.dap/ptrref.cc  |  34 +++++++++++++
 gdb/testsuite/gdb.dap/ptrref.exp | 103 +++++++++++++++++++++++++++++++++++++++
 gdb/valarith.c                   |   6 +--
 15 files changed, 303 insertions(+), 110 deletions(-)
---
base-commit: a006bc9c37e95b4afaf85715cc54fe57b3300ccd
change-id: 20230905-dap-30821-pointers-6b62c5cb8a9f

Best regards,
-- 
Tom Tromey <tromey@adacore.com>


             reply	other threads:[~2023-09-05 19:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05 19:47 Tom Tromey [this message]
2023-09-05 19:47 ` [PATCH 1/5] Pass a type allocator to init_fixed_point_type Tom Tromey
2023-09-05 19:47 ` [PATCH 2/5] Regularize some DWARF type initialization Tom Tromey
2023-09-05 19:47 ` [PATCH 3/5] Add is_array_like and to_array to language_defn Tom Tromey
2023-09-05 19:47 ` [PATCH 4/5] Give a language to a type Tom Tromey
2023-09-05 19:47 ` [PATCH 5/5] Handle pointers and references correctly in DAP Tom Tromey
2023-09-19 19:30 ` [PATCH 0/5] " Tom Tromey

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=20230905-dap-30821-pointers-v1-0-0d7323327678@adacore.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).