From c0b48ab6318026121241f90430b337ea2c7ee384 Mon Sep 17 00:00:00 2001 From: Jonas Devlieghere Date: Wed, 8 May 2019 01:23:47 +0000 Subject: Propagate command interpreter errors from lldlbinit This patch ensures that we propagate errors coming from the lldbinit file trough the command/script interpreter. Before, if you did something like command script import syntax_error.py, and the python file contained a syntax error, lldb wouldn't tell you about it. This changes with the current patch: errors are now propagated by default. PS: Jim authored this change and I added testing. Differential revision: https://reviews.llvm.org/D61579 llvm-svn: 360216 --- lldb/source/Commands/CommandObjectWatchpointCommand.cpp | 1 + 1 file changed, 1 insertion(+) (limited to 'lldb/source/Commands/CommandObjectWatchpointCommand.cpp') diff --git a/lldb/source/Commands/CommandObjectWatchpointCommand.cpp b/lldb/source/Commands/CommandObjectWatchpointCommand.cpp index 3c8eb59..8be6688 100644 --- a/lldb/source/Commands/CommandObjectWatchpointCommand.cpp +++ b/lldb/source/Commands/CommandObjectWatchpointCommand.cpp @@ -295,6 +295,7 @@ are no syntax errors may indicate that a function was declared but never called. options.SetStopOnError(data->stop_on_error); options.SetEchoCommands(false); options.SetPrintResults(true); + options.SetPrintErrors(true); options.SetAddToHistory(false); debugger.GetCommandInterpreter().HandleCommands(commands, &exe_ctx, -- cgit v1.1