From: Yao Qi <qiyaoltc@gmail.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Show optimized out local variables in "info locals"
Date: Tue, 14 Nov 2017 22:44:00 -0000 [thread overview]
Message-ID: <CAH=s-PN-d3Dg0VRWZMQGrQ8D8owF_eii=X4JrOPnRVS7=JkVfQ@mail.gmail.com> (raw)
In-Reply-To: <1510679293-8244-1-git-send-email-simon.marchi@ericsson.com>
On Tue, Nov 14, 2017 at 5:08 PM, Simon Marchi <simon.marchi@ericsson.com> wrote:
>
> However, this change reveals what I think is a bug in GDB, see:
>
> http://lists.dwarfstd.org/pipermail/dwarf-discuss-dwarfstd.org/2017-September/004394.html
>
IMO, it is not necessary to emit DW_TAG_lexical_block in concrete instances.
See comment #4 in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37801
At least, looks gcc generates unnecessary debug information, and we need
to fix GCC somehow.
Whether it is a bug in GDB or not, I don't know. The answer depends on it is
*unnecessary* or *wrong* to have DW_TAG_lexical_block in concrete instances.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-11-14 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 17:08 Simon Marchi
2017-11-14 22:44 ` Yao Qi [this message]
2017-11-15 4:54 ` Simon Marchi
2017-11-22 20:58 ` Simon Marchi
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='CAH=s-PN-d3Dg0VRWZMQGrQ8D8owF_eii=X4JrOPnRVS7=JkVfQ@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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