Fixes [#68035](https://github.com/llvm/llvm-project/issues/68035), where an inconsistency in the order of "Process launched" and "Process stopped" messages occurs during `process launch`. The fix involves adjusting the message output sequence in `CommandObjectProcessLaunch::DoExecute` within `source/Commands/CommandObjectProcess.cpp`. This ensures "Process launched" consistently precedes "Process stopped" when executing commands with the '-o' flag, i.e., non-interactive mode. Upon implementing this change, two tests failed: `lldb/test/Shell/Breakpoint/jit-loader_jitlink_elf.test` and `lldb/test/Shell/Breakpoint/jit-loader_rtdyld_elf.test`. These failures were expected as they relied on the previous, now-corrected message order. Updating these tests to align with the new message sequence is part of this PR's scope.
19 lines
701 B
Plaintext
19 lines
701 B
Plaintext
# REQUIRES: target-x86_64
|
|
# XFAIL: system-windows
|
|
|
|
# JITLink is the Orc-specific JIT linker implementation.
|
|
#
|
|
# RUN: %clang -g -S -emit-llvm -fPIC --target=x86_64-unknown-unknown-elf \
|
|
# RUN: -o %t.ll %p/Inputs/jitbp.cpp
|
|
# RUN: %lldb -b -o 'settings set plugin.jit-loader.gdb.enable on' -o 'b jitbp' \
|
|
# RUN: -o 'run --jit-linker=jitlink %t.ll' lli | FileCheck %s
|
|
|
|
# CHECK: Breakpoint 1: no locations (pending).
|
|
# CHECK: (lldb) run {{.*}}
|
|
# CHECK: Process {{.*}} launched: {{.*}}
|
|
# CHECK: Process {{.*}} stopped
|
|
# CHECK: JIT(0x{{.*}})`jitbp() at jitbp.cpp:1:15
|
|
# CHECK: -> 1 int jitbp() { return 0; }
|
|
# CHECK: ^
|
|
# CHECK: 2 int main() { return jitbp(); }
|