Actually emit a warning, rather than an error, when there's an .lldbinit file in the current directly. Currently, the message is prepended by "error" which looks rather odd, as the warning refers to itself as a warning.
17 lines
826 B
Plaintext
17 lines
826 B
Plaintext
# REQUIRES: python
|
|
#
|
|
# RUN: mkdir -p %t.root
|
|
# RUN: mkdir -p %t.home
|
|
# RUN: cp %S/Inputs/.lldbinit %t.root
|
|
# RUN: cp %S/Inputs/syntax_error.py %t.root
|
|
# RUN: cd %t.root
|
|
# RUN: env HOME=%t.home %lldb-init -o 'settings show frame-format' 2>&1 | FileCheck %s --check-prefix=WARNINIT --check-prefix=CHECK
|
|
# RUN: env HOME=%t.home %lldb-init -local-lldbinit -o 'settings show frame-format' 2>&1 | FileCheck %s --check-prefix=ALLOWINIT --check-prefix=NOINIT
|
|
# RUN: %lldb -o 'settings show frame-format' 2>&1 | FileCheck %s --check-prefix=NOINIT --check-prefix=CHECK
|
|
|
|
# WARNINIT: warning: There is a .lldbinit file in the current directory which is not being read.
|
|
# NOINIT-NOT: There is a .lldbinit file in the current directory which is not being read.
|
|
# CHECK-NOT: bogus
|
|
# ALLOWINIT: name 'prlnt' is not defined
|
|
# ALLOWINIT: bogus
|