JDevlieghere added a comment. I'm seeing some really weird behavior for the following two tests and I'm honestly kind of puzzled.
ObjectFile/ELF/PT_LOAD-overlap-PT_TLS.yaml ObjectFile/ELF/PT_TLS-overlap-PT_LOAD.yaml They fail in the same way for a standalone build, both on macOS (http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-standalone/1009/) and Linux (https://ci.swift.org/view/swift-master-rebranch/job/oss-lldb-master-rebranch-incremental-linux-ubuntu-18_04/8/). For a standalone build the image lookups returns: (lldb) image lookup -a 0x1000 Address: PT_LOAD-overlap-PT_TLS.yaml.tmp[0x00001000] (PT_LOAD-overlap-PT_TLS.yaml.tmp..tbss + 0) While for a regular in-tree build the image lookup returns: (lldb) image lookup -a 0x1000 Address: PT_LOAD-overlap-PT_TLS.yaml.tmp[0x00001000] (PT_LOAD-overlap-PT_TLS.yaml.tmp.PT_LOAD[0]..data + 0) I scp'd the binaries between my local machine and the bot and they don't affect the outcome, it's just lldb that's different... Pavel, can you think of *anything* that might cause this? Repository: rL LLVM CHANGES SINCE LAST ACTION https://reviews.llvm.org/D65282/new/ https://reviews.llvm.org/D65282 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
