From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch] Fix C `extern' shadowing in a local block
Date: Sat, 28 Mar 2009 23:29:00 -0000 [thread overview]
Message-ID: <20090328213753.GA16821@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20090326212128.GA32657@host0.dyn.jankratochvil.net>
On Thu, 26 Mar 2009 22:21:28 +0100, Jan Kratochvil wrote:
> fix GDB evaluation for:
> {
> int var = 1;
> {
> extern int var;
>
> Access "var" at this point from GDB which must access the `extern' variable.
> }
> }
>
> Such code will still not work due to GCC PR debug/39563. GCC may also fix it
> a way compatible with current GDB (`extern var' to be global and use
> DW_TAG_imported_declaration in the local block). Still IMO a valid DWARF
> layout used in the attached .S testcase currently fails for GDB.
The patch provided for GCC (but still not checked-in) requires fixed GDB:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39563#c5
Thanks,
Jan
next prev parent reply other threads:[~2009-03-28 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 21:38 Jan Kratochvil
2009-03-28 23:29 ` Jan Kratochvil [this message]
2009-04-02 18:54 ` Joel Brobecker
2009-04-02 19:06 ` Daniel Jacobowitz
2009-04-02 21:08 ` Jan Kratochvil
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=20090328213753.GA16821@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.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