Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/2] [gdb] Enable ptype /o for some dynamic types
Date: Wed, 11 Mar 2026 12:55:04 +0100	[thread overview]
Message-ID: <20260311115506.3101288-1-tdevries@suse.de> (raw)

This patch series fixes PR33966.

The first patch refactors is_dynamic_types_internal.

The second patch contains the fix.

Tested on x86_64-linux.

Changes in v2:
- committed the first patch of v1
- updated the first patch to not expose the top_level parameter in
  is_dynamic_types
- updated the second patch by:
  - hoisting a check
  - moving the tests to a new testcase gdb.base/ptype-offsets-c.exp

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

Tom de Vries (2):
  [gdb] Factor out is_dynamic_type_internal_1
  [gdb] Enable ptype /o for some dynamic types

 gdb/gdbtypes.c                             | 68 ++++++++++++++++++----
 gdb/gdbtypes.h                             |  4 ++
 gdb/testsuite/gdb.ada/ptype-o.exp          |  2 +-
 gdb/testsuite/gdb.base/ptype-offsets-c.c   | 37 ++++++++++++
 gdb/testsuite/gdb.base/ptype-offsets-c.exp | 63 ++++++++++++++++++++
 gdb/typeprint.c                            |  4 +-
 6 files changed, 163 insertions(+), 15 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/ptype-offsets-c.c
 create mode 100644 gdb/testsuite/gdb.base/ptype-offsets-c.exp


base-commit: fe97d7c31d7e81eec11243e269139a08632d085f
-- 
2.51.0


             reply	other threads:[~2026-03-11 11:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 11:55 Tom de Vries [this message]
2026-03-11 11:55 ` [PATCH v2 1/2] [gdb] Factor out is_dynamic_type_internal_1 Tom de Vries
2026-03-11 11:55 ` [PATCH v2 2/2] [gdb] Enable ptype /o for some dynamic types Tom de Vries
2026-03-25 12:48 ` [PING][PATCH v2 0/2] " Tom de Vries
2026-04-02 15:38 ` [PATCH " Guinevere Larsen
2026-04-03 13:20   ` Tom de Vries

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=20260311115506.3101288-1-tdevries@suse.de \
    --to=tdevries@suse.de \
    --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