From: Tom Tromey <tom@tromey.com>
To: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] Remove gdb_assert for TYPE_CODE_METHOD in stabs reader
Date: Thu, 22 Oct 2020 11:21:49 -0600 [thread overview]
Message-ID: <87k0vi89ci.fsf@tromey.com> (raw)
In-Reply-To: <20201006154928.3298-2-ssbssa@yahoo.de> (Hannes Domani via Gdb-patches's message of "Tue, 6 Oct 2020 17:49:28 +0200")
>>>>> "Hannes" == Hannes Domani via Gdb-patches <gdb-patches@sourceware.org> writes:
Hannes> It's possible to come across TYPE_CODE_UNDEF at this point in
Hannes> read_member_functions, which according to a comment in read_type
Hannes> is used for forward references.
Hannes> gdb/ChangeLog:
Hannes> 2020-10-06 Hannes Domani <ssbssa@yahoo.de>
Hannes> * stabsread.c (read_member_functions): Remove gdb_assert.
Ok. Thanks for the patch.
Tom
next prev parent reply other threads:[~2020-10-22 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201006154928.3298-1-ssbssa.ref@yahoo.de>
2020-10-06 15:49 ` [PATCH 1/2] Don't create _Complex type name if there is no target type name Hannes Domani
2020-10-06 15:49 ` [PATCH 2/2] Remove gdb_assert for TYPE_CODE_METHOD in stabs reader Hannes Domani
2020-10-22 17:21 ` Tom Tromey [this message]
2020-10-22 17:21 ` [PATCH 1/2] Don't create _Complex type name if there is no target type name Tom Tromey
2020-10-22 17:40 ` Hannes Domani
2020-10-22 17:46 ` Tom Tromey
2020-10-22 18:20 ` Hannes Domani
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=87k0vi89ci.fsf@tromey.com \
--to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).