[Bug d/31580] New: Regression in D class type resolution since GDB 10

["liushuyu011 at gmail dot com" <sourceware-bugzilla@sourceware.org>]

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

            Bug ID: 31580
           Summary: Regression in D class type resolution since GDB 10
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: d
          Assignee: unassigned at sourceware dot org
          Reporter: liushuyu011 at gmail dot com
  Target Milestone: ---

Created attachment 15447
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15447&action=edit
Minimal reproducible example (D source code)

Hi there,

I have discovered a D class type resolution regression since GDB 10 (it was
working properly in GDB 9).

Please find the reproducer in the file attached. You can compile the source
code using either GDC or LDC2 (both can reproduce this issue):

gdc -g -O0 t.d -o t

To reproduce the bug, set the breakpoint to t.d:10 and examine the `i` global
variable (using `p t.i`). GDB will then complain that "'t.i' has unknown type;
cast it to its declared type."

I found a workaround to this problem by using `p (uv*)_D1t1iCQf2uv`, but
obviously, this is non-ideal: the developer may not know the mangled variable
name easily.

Since this looks like a regression, I did a simple `git bisect` that led me to
this commit:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=727b7b1864973c2645a554727afd0eaf1303673a.
I am unsure how demangle changes could affect the type resolution (maybe it's
because GDB got confused about which entity to decode?)

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