public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/28127] DW_FORM_data16 support Date: Fri, 23 Jul 2021 15:04:17 +0000 [thread overview] Message-ID: <bug-28127-4717-igGTcI4pBa@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28127-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28127 --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- With this: ... $ git diff diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c index 029b8bfad04..8b603e8acae 100644 --- a/gdb/dwarf2/read.c +++ b/gdb/dwarf2/read.c @@ -18247,6 +18247,9 @@ attr_to_dynamic_prop (const struct attribute *attr, struct die _info *die, if (attr == NULL || prop == NULL) return 0; + if (attr->form == DW_FORM_data16) + return 0; + if (attr->form_is_block ()) { baton = XOBNEW (obstack, struct dwarf2_property_baton); ... we have: ... (gdb) PASS: gdb.ada/arrayptr.exp: scenario=all: ptype string_access print pa_ptr.all^M $7 = (10, 20, 30, 40, 50, 60, 62, 63, -23, 42)^M (gdb) PASS: gdb.ada/arrayptr.exp: scenario=all: print pa_ptr.all ... but also with set complaints 1000: ... During symbol reading: Unresolved DW_AT_upper_bound - DIE at 0x1528 [in module foo] ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-07-23 15:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-23 14:33 [Bug symtab/28127] New: " vries at gcc dot gnu.org 2021-07-23 15:04 ` vries at gcc dot gnu.org [this message] 2021-07-23 15:11 ` [Bug symtab/28127] " vries at gcc dot gnu.org 2021-07-25 7:25 ` vries at gcc dot gnu.org 2023-03-07 0:45 ` tromey at sourceware dot org 2023-03-07 14:10 ` tromey at sourceware dot org
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-28127-4717-igGTcI4pBa@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: linkBe 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).