From: Daniel Colascione <dancol@dancol.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Fix infinite loop in update_enumeration_type_from_children
Date: Sun, 09 Nov 2014 22:05:00 -0000 [thread overview]
Message-ID: <545FE524.5070607@dancol.org> (raw)
In-Reply-To: <CADPb22QvBYWaYMGwpUEwk5K1AbRKqQBgRGK8vrgigR2VTzifhA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 277 bytes --]
On 10/08/2014 06:58 AM, Doug Evans wrote:
> Changing the loop to a for loop is another way to go, and arguably preferable.
Either way, it looks like this bug is unfixed in master. Now that I have
papers, can this patch (or an equivalent for-loop version) be committed?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-09 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 20:50 Daniel Colascione
2014-10-07 18:07 ` Pedro Alves
2014-10-08 5:58 ` Doug Evans
2014-11-09 22:05 ` Daniel Colascione [this message]
2014-11-12 15:52 ` Doug Evans
2014-11-14 0:39 ` [COMMITTED PATCH] " Doug Evans
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=545FE524.5070607@dancol.org \
--to=dancol@dancol.org \
--cc=dje@google.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