From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/symtab] Fix element type modification in read_array_type
Date: Tue, 09 Feb 2021 13:24:59 -0700 [thread overview]
Message-ID: <87o8gtat0k.fsf@tromey.com> (raw)
In-Reply-To: <8b89b73a-205b-0da0-26fe-8d5e45a10886@suse.de> (Tom de Vries's message of "Sun, 7 Feb 2021 09:38:43 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> + {
Tom> + complaint (_("unable to handle array child DIE %s"
Tom> + " - DIE at %s [in module %s]"),
Tom> + dwarf_tag_name (child_die->tag),
Tom> + sect_offset_str (die->sect_off),
Tom> + objfile_name (cu->per_objfile->objfile));
Tom> + return NULL;
Tom> + }
This seems a bit too strong to me. A normal DWARF extension mechanism
is to add new "unexpected" children to a DIE. In many (maybe most)
cases, it's fine to just ignore these.
Maybe another approach would be to bail out if range_types.empty(),
issuing a complaint then. This wouldn't mention
DW_TAG_generic_subrange, but that seems ok to me.
Users don't really read complaints. Maybe even gdb developers don't ;)
Tom
next prev parent reply other threads:[~2021-02-09 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 12:28 Tom de Vries
2021-02-05 16:30 ` Tom Tromey
2021-02-07 8:38 ` Tom de Vries
2021-02-09 20:24 ` Tom Tromey [this message]
2021-02-09 22:29 ` Tom de Vries
2021-02-10 12:23 ` 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=87o8gtat0k.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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