=?utf-8?q?José?= L. Junior <josejun...@10xengineers.ai> Message-ID: In-Reply-To: <llvm.org/llvm/llvm-project/pull/69...@github.com>
DavidSpickett wrote: > While I was working in the test you recommended, I noticed the following: if > I run image lookup -r -s UNEXPECTED_PATTERN through the '-o' flag, any > command passed after that with another '-o' flag will not be executed, i.e., This is expected, lldb stops if one of those commands fails. It just so happens that `image lookup` does not print a message on finding no symbols. https://github.com/llvm/llvm-project/blob/6e56c35d1959295289734baf8924d477f770d6f8/lldb/source/Commands/CommandObjectTarget.cpp#L4209 Presumably because to a user on the interactive command line, if they get no output they'll likely assume no symbols found. If you do this with some command that does fail in a verbose way, it'll make more sense: ``` $ ./bin/lldb -o "foo" -o "help" (lldb) foo error: 'foo' is not a valid command. (lldb) ``` https://github.com/llvm/llvm-project/pull/69422 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
