[Bug symtab/25695] New: abstract and concrete variable listed both with "info locals"

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=25695

            Bug ID: 25695
           Summary: abstract and concrete variable listed both with "info
                    locals"
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

There's an open issue described in
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=41bd68f52c05f5654bed49f312f6562c8d048897
:
...
Show optimized out local variables in "info locals"

Currently, optimized out variables are not shown when doing "info
locals".  Some users found that confusing, thinking GDB forgot to print
their variable.  This patch adds them to the "info locals" output.  I
added a test in gdb.dwarf2 to test for that behavior.  I think doing a
synthetic DWARF test is the easiest way to have an optimized out local
variable for sure.

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

This patch marks the tests in inline-locals.exp that start failing as
KFAIL.  I'd like to tackle this bug eventually, but I don't have the
time right now.  I think it's still better to show an extra erroneous
entry than to not show the optimized out variables at all.  I haven't
created a bug in bugzilla yet, but if we agree it's indeed a bug,  I'll
create one and update the setup_kfail lines with the actual bug number
before pushing.
...

The KFAILs have been like this:
...
    setup_kfail "gdb/xyz" *-*-*
...
for more than two years now.

Let's have this PR in bugzilla at least to keep track of the KFAIls.

-- 
You are receiving this mail because:
You are on the CC list for the bug.