From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <xdje42@gmail.com>
Cc: lin zuojian <manjian2006@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Tom Tromey <tromey@redhat.com>, linzj <linzj@ucweb.com>
Subject: Re: PING: [PATCH v4] fixed inherit_abstract_dies infinite recursive call
Date: Wed, 19 Feb 2014 07:59:00 -0000 [thread overview]
Message-ID: <20140219075900.GC4270@adacore.com> (raw)
In-Reply-To: <m3mwhnvbrk.fsf@sspiff.org>
> Hi.
> Sorry for the delay!
No, Thank You for looking into it! :)
> I spent some time looking for a cleverer patch, but in the end I think the
> simplicity of this patch is nice.
:)
>
> 2014-02-18 lin zuojian <manjian2006@gmail.com>
> Joel Brobecker <brobecker@adacore.com>
> Doug Evans <xdje42@gmail.com>
>
> PR symtab/16581
> * dwarf2read.c (struct die_info): New member in_process.
> (reset_die_in_process): New function.
> (process_die): Set it at the start, reset when returning.
> (inherit_abstract_dies): Only call process_die if origin_child_die
> not already being processed.
>
> testsuite/
> * gdb.dwarf2/dw2-icycle.S: New file.
> * gdb.dwarf2/dw2-icycle.c: New file.
> * gdb.dwarf2/dw2-icycle.exp: New file.
That looks good to me, with one tiny little CS comment (see below).
> +static void
> +reset_die_in_process (void *arg)
> +{
> + struct die_info *die = arg;
> + die->in_process = 0;
Missing empty line after local variable declaration.
Thanks again,
--
Joel
next prev parent reply other threads:[~2014-02-19 7:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 7:07 manjian2006
2014-01-28 12:06 ` Joel Brobecker
2014-02-10 14:28 ` PING: " Joel Brobecker
2014-02-10 17:37 ` Doug Evans
2014-02-11 2:19 ` Joel Brobecker
2014-02-12 6:58 ` Doug Evans
2014-02-13 7:31 ` Joel Brobecker
2014-02-13 8:01 ` lin zuojian
2014-02-14 3:34 ` Joel Brobecker
2014-02-19 6:48 ` Doug Evans
2014-02-19 7:00 ` lin zuojian
2014-02-19 7:59 ` Joel Brobecker [this message]
2014-02-20 17:18 ` Doug Evans
2014-02-20 17:48 ` Joel Brobecker
2014-02-12 1:29 ` manjian2006
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=20140219075900.GC4270@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=linzj@ucweb.com \
--cc=manjian2006@gmail.com \
--cc=tromey@redhat.com \
--cc=xdje42@gmail.com \
/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