ljmf00 added a comment. In D117928#3262656 <https://reviews.llvm.org/D117928#3262656>, @JDevlieghere wrote:
> Why are we disabling a lldb test because of a bug in GDB? Because GDB is used on systems that don't implement a `RegisterContext`. I added an inline comment about Darwin and Windows XFAIL, as I'm not sure if this is just Linux specific. See here https://github.com/llvm/llvm-project/blob/main/lldb/source/Plugins/Process/gdb-remote/GDBRemoteRegisterContext.cpp#L296 . Take a look at the issue. You can also reproduce this with `register write`/`register read` right after. This ended up breaking my testsuite for a long time, since my server has an x86-64-v2 CPU, instead of an x86-64-v3. The buildbots seem to have at least x86-64-v3. As described by the issue I tested this on an AVX capable machine (x86-64-v3) and virtualized an older CPU to reproduce in a clean environment. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D117928/new/ https://reviews.llvm.org/D117928 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
