From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: [patch] Fix crash on reading gcc HEAD Fortran module
Date: Mon, 01 Sep 2008 16:51:00 -0000 [thread overview]
Message-ID: <20080901165107.GA7457@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20080901152956.GA15230@caradoc.them.org>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
On Mon, 01 Sep 2008 17:29:56 +0200, Daniel Jacobowitz wrote:
> please complain about children in DW_TAG_imported_declaration even in
> Fortran (see the comment above your change).
Originally I expected these complaints are just for detected DWARF violations:
_("Offset %d out of bounds for DW_AT_ranges attribute"),
But they are produced even just for unsupported DWARF features:
complaint (&symfile_complaints, _("unsupported tag: '%s'"),
Therefore it should always complain to any such DW_TAG_imported_* tag as they
are always at least unsupported. (And it does not matter if some of their
forms with or without children are invalid for DWARF or not.)
[ approval requested ]
Thanks,
Jan
[-- Attachment #2: gdb-cvs-module-import.patch --]
[-- Type: text/plain, Size: 994 bytes --]
2008-09-01 Jan Kratochvil <jan.kratochvil@redhat.com>
Stay compatible after the GCC PR fortran/29635 fix.
* dwarf2read.c (process_die <DW_TAG_imported_module>)
(process_die <DW_TAG_imported_module>): Do not assert anything about
these unsupported tags.
--- ./gdb/dwarf2read.c 29 Aug 2008 17:06:05 -0000 1.278
+++ ./gdb/dwarf2read.c 1 Sep 2008 16:35:17 -0000
@@ -2760,10 +2760,10 @@ process_die (struct die_info *die, struc
information contained in these. DW_TAG_imported_declaration
dies shouldn't have children; DW_TAG_imported_module dies
shouldn't in the C++ case, but conceivably could in the
- Fortran case, so we'll have to replace this gdb_assert if
- Fortran compilers start generating that info. */
+ Fortran case. */
processing_has_namespace_info = 1;
- gdb_assert (die->child == NULL);
+ complaint (&symfile_complaints, _("unsupported tag: '%s'"),
+ dwarf_tag_name (die->tag));
break;
default:
new_symbol (die, NULL, cu);
next prev parent reply other threads:[~2008-09-01 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 13:02 Jan Kratochvil
2008-09-01 15:30 ` Daniel Jacobowitz
2008-09-01 16:51 ` Jan Kratochvil [this message]
2008-09-01 22:18 ` Daniel Jacobowitz
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=20080901165107.GA7457@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=drow@false.org \
--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