Michael137 wrote:
> @Michael137 This broke the windows bot:
> https://lab.llvm.org/buildbot/#/builders/141/builds/1214 Should we skip it on
> that platform or do you see an easy fix ?
Thanks for pinging. This is the failure:
```
| error: no variable named 'f' found in this frame
# `-----------------------------
# executed command:
'c:\users\tcwg\llvm-worker\lldb-aarch64-windows\build\bin\filecheck.exe'
'C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\llvm-project\lldb\test\Shell\SymbolFile\DWARF\vla.cpp'
# .---command stderr------------
# |
C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\llvm-project\lldb\test\Shell\SymbolFile\DWARF\vla.cpp:26:17:
error: CHECK-NEXT: expected string not found in input
# | // CHECK-NEXT: (Foo) f = {
# | ^
# | <stdin>:16:32: note: scanning from here
# | (lldb) frame var --show-types f
# | ^
# |
# | Input file: <stdin>
# | Check file:
C:\Users\tcwg\llvm-worker\lldb-aarch64-windows\llvm-project\lldb\test\Shell\SymbolFile\DWARF\vla.cpp
# |
# | -dump-input=help explains the following input dump.
# |
# | Input was:
# | <<<<<<
# | .
# | .
# | .
# | 11: vla.cpp.tmp`main:
# | 12: -> 0x7ff66e41eb18 <+396>: ldur x8, [x29, #-0x28]
# | 13: 0x7ff66e41eb1c <+400>: mov sp, x8
# | 14: 0x7ff66e41eb20 <+404>: ldur w0, [x29, #-0x4]
# | 15: 0x7ff66e41eb24 <+408>: mov sp, x29
# | 16: (lldb) frame var --show-types f
# | next:26 X error: no match found
# | >>>>>>
# `-----------------------------
```
Looks strange. Not sure why it's not finding the symbols properly.
I'm tempted to skip this on Windows since I don't have an LLDB setup to test
this on. @DavidSpickett Am I remembering correctly that you might have an
AArch64 Windows setup? If so, does this reproduce for you? I'm confused as to
why the debug symbols don't seem to be found.
https://github.com/llvm/llvm-project/pull/100710
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
