From: manjian2006@gmail.com
To: gdb-patches@sourceware.org, tromey@redhat.com, brobecker@adacore.com
Cc: linzj <linzj@ucweb.com>
Subject: Re: Re: [PATCH] fixed inherit_abstract_dies infinite recursive call
Date: Tue, 21 Jan 2014 10:17:00 -0000 [thread overview]
Message-ID: <1390299395-16618-1-git-send-email-manjian2006@gmail.com> (raw)
In-Reply-To: <20140121075427.GY4762@adacore.com>
From: linzj <linzj@ucweb.com>
I don't think my patch is able to fill the hole of DWARF specs,and there my not be
any hole.
My patch is adding a bit to die and actully form a bitmap when processing dwarf byte code.
If you think process_die as graph traversal,that bitmap is to avoid visiting a node twice.
I post duplicatly simply because I don't know how to use mail list.
I will add the change logs in next patch.
I change the source so few,I don't think an FSF assignment is needed(not more than 10 lines).
next prev parent reply other threads:[~2014-01-21 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 4:25 manjian2006
2014-01-20 5:53 ` Tom Tromey
2014-01-21 1:43 ` manjian2006
2014-01-21 7:54 ` Joel Brobecker
2014-01-21 10:17 ` manjian2006 [this message]
2014-01-20 6:30 ` manjian2006
2014-01-22 2:45 ` 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=1390299395-16618-1-git-send-email-manjian2006@gmail.com \
--to=manjian2006@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=linzj@ucweb.com \
--cc=tromey@redhat.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