[llvm-bugs] [Bug 35524] [CodeView] Range-based for loop variables are not available when debugging

via llvm-bugs llvm-bugs at lists.llvm.org
Wed Dec 20 15:02:42 PST 2017


Reid Kleckner <rnk at google.com> changed:

           What    |Removed                     |Added
         Resolution|---                         |DUPLICATE
             Status|NEW                         |RESOLVED

--- Comment #3 from Reid Kleckner <rnk at google.com> ---
I think the trouble is that there are really two range-based for loops and two
variables named 'S'. Here's what I see in windbg:

0:000> dv
                      CP = 0x00000078`c738f458
CurrentSectionDataOffset = 0xb7c
                 __range = 0x00000267`4e329020 { size=73 }
                 __begin = {...}
                   __end = {...}
                       S = 0x00000267`4e35b380  # Valid S
                 __range = <value unavailable>
                 __begin = <value unavailable>
                   __end = <value unavailable>
                       S = <value unavailable>  # Probably for the next loop
        SymbolTableStart = 0x7ff7
         NumberOfSymbols = 0x88e3e8ce
                       i = <value unavailable>
                       e = <value unavailable>
      NumberOfAuxSymbols = <value unavailable>

I'd dupe this against "we should implement S_BLOCK32 scopes".

*** This bug has been marked as a duplicate of bug 28458 ***

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20171220/7ed496e1/attachment.html>

More information about the llvm-bugs mailing list