cmtice added a comment. It is true that the compiler will not know where the final executable will be placed, and if the executable gets moved then debugging with .dwo files will probably not work anyway, However as it is currently written, LLDB will fail to find the .dwo files, *even when the binary has not been moved*, if the debugger is launched from any directory other than the one containing the binary.
E.g. we have a team where the standard workflow is 'cd src'; build binary in src/out/Debug/.; from src, do 'lldb out/Debug/binary'. lldb cannot find the .dwo files. re "GDB does it this way" -- I am also writing/submitting a patch to get GDB to change this behavior. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D97786/new/ https://reviews.llvm.org/D97786 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
