Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Avoid resolving dynamic properties for non-allocated arrays
Date: Wed, 23 Dec 2020 23:53:53 +0000	[thread overview]
Message-ID: <cover.1608767467.git.andrew.burgess@embecosm.com> (raw)

Fix for issue PR gdb/27059 in patch #2, with a small helper patch in #1.

All feedback welcome.

Thanks,
Andrew


---

Andrew Burgess (2):
  gdb: include allocated/associated properties in 'maint print type'
  gdb: avoid resolving dynamic properties for non-allocated arrays

 gdb/ChangeLog                                 |  19 +++
 gdb/eval.c                                    |  12 +-
 gdb/f-lang.c                                  |   4 +
 gdb/gdbtypes.c                                |  87 ++++++++++---
 gdb/testsuite/ChangeLog                       |   6 +
 .../gdb.dwarf2/dyn-type-unallocated.c         |  40 ++++++
 .../gdb.dwarf2/dyn-type-unallocated.exp       | 122 ++++++++++++++++++
 7 files changed, 266 insertions(+), 24 deletions(-)
 create mode 100644 gdb/testsuite/gdb.dwarf2/dyn-type-unallocated.c
 create mode 100644 gdb/testsuite/gdb.dwarf2/dyn-type-unallocated.exp

-- 
2.25.4


             reply	other threads:[~2020-12-23 23:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-23 23:53 Andrew Burgess [this message]
2020-12-23 23:53 ` [PATCH 1/2] gdb: include allocated/associated properties in 'maint print type' Andrew Burgess
2020-12-24  5:41   ` Simon Marchi via Gdb-patches
2020-12-23 23:53 ` [PATCH 2/2] gdb: avoid resolving dynamic properties for non-allocated arrays Andrew Burgess
2020-12-24 14:46   ` Simon Marchi via Gdb-patches
2020-12-24 17:04     ` Andrew Burgess

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=cover.1608767467.git.andrew.burgess@embecosm.com \
    --to=andrew.burgess@embecosm.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