weliveindetail wrote: Hi @rastogishubham thanks for acting on this! The log of this particular run was deleted already, but https://green.lab.llvm.org/job/llvm.org/view/LLDB/job/as-lldb-cmake/13958 likely failed for the same reason: ``` lldb-build/bin/clang --driver-mode=cl --target=specify-a-target-or-use-a-_host-substitution --target=x86_64-windows-msvc -c -gdwarf /Users/ec2-user/jenkins/workspace/llvm.org/as-lldb-cmake/llvm-project/lldb/test/Shell/SymbolFile/DWARF/x86/member-pointers.cpp -o /Users/ec2-user/jenkins/workspace/llvm.org/as-lldb-cmake/lldb-build/tools/lldb/test/Shell/SymbolFile/DWARF/x86/Output/member-pointers.cpp.tmp_win.obj clang: warning: '/Users/ec2-user/jenkins/workspace/llvm.org/as-lldb-cmake/llvm-project/lldb/test/Shell/SymbolFile/DWARF/x86/member-pointers.cpp' treated as the '/U' option [-Wslash-u-filename] clang: note: use '--' to treat subsequent arguments as filenames clang: error: no input files ```
Apparently, `/U` is an option for the clang `cl` mode driver and this collides with the start of the file name path in `/Users/...`. Let me prepare a patch for it. https://github.com/llvm/llvm-project/pull/112928 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
