// Tests that ProcessModID.m_memory_id is not bumped when evaluating expressions without side effects. // REQUIRES: target-windows && (target-x86 || target-x86_64) // Due to different implementations exact numbers (m_stop_id) are different on different OSs. So we lock this test to specific platform (Windows). It is limited to x86/x64 because on x86/x64, running get() // requires that we write the return address to the stack, this does not happen on AArch64. // RUN: %build %s -o %t // RUN: %lldb %t \ // RUN: -o "settings set target.process.track-memory-cache-changes false" \ // RUN: -o "run" \ // RUN: -o "process status -d" \ // RUN: -o "expr x.i != 42" \ // RUN: -o "process status -d" \ // RUN: -o "process status -d" \ // RUN: -o "expr x.get()" \ // RUN: -o "process status -d" \ // RUN: -o "process status -d" \ // RUN: -o "expr x.i = 10" \ // RUN: -o "process status -d" \ // RUN: -o "process status -d" \ // RUN: -o "continue" \ // RUN: -o "process status -d" \ // RUN: -o "exit" | FileCheck %s -dump-input=fail class X { int i = 0; public: int get() { return i; } }; int main() { X x; x.get(); __builtin_debugtrap(); __builtin_debugtrap(); return 0; } // CHECK-LABEL: process status -d // CHECK: m_stop_id: [[#STOP_ID:]] // CHECK: m_memory_id: [[#MEMORY_ID:]] // CHECK-LABEL: expr x.i != 42 // IDs are not changed when executing simple expressions // CHECK-LABEL: process status -d // CHECK: m_stop_id: [[#STOP_ID]] // CHECK: m_memory_id: [[#MEMORY_ID]] // CHECK-LABEL: process status -d // Remember new values // CHECK: m_stop_id: [[#STOP_ID:]] // CHECK: m_memory_id: [[#MEMORY_ID:]] // CHECK-LABEL: expr x.get() // Expression causes ID to be bumped because LLDB has to execute function and in doing // so must write the return address to the stack. // CHECK-LABEL: process status -d // CHECK-NOT: m_stop_id: [[#STOP_ID]] // CHECK-NOT: m_memory_id: [[#MEMORY_ID]] // CHECK-LABEL: process status -d // Remember new values // CHECK: m_stop_id: [[#STOP_ID:]] // CHECK: m_memory_id: [[#MEMORY_ID:]] // CHECK-LABEL: expr x.i = 10 // Expression causes MemoryID to be bumped because LLDB writes to non-cache memory // CHECK-LABEL: process status -d // CHECK: m_stop_id: [[#STOP_ID]] // CHECK-NOT: m_memory_id: [[#MEMORY_ID]] // CHECK-LABEL: process status -d // Remember new values // CHECK: m_stop_id: [[#STOP_ID:]] // CHECK: m_memory_id: [[#MEMORY_ID:]] // CHECK-LABEL: continue // Continue causes StopID to be bumped because process is resumed // CHECK-LABEL: process status -d // CHECK-NOT: m_stop_id: [[#STOP_ID]] // CHECK: m_memory_id: [[#MEMORY_ID]]