mirror of
https://github.com/intel/llvm.git
synced 2026-01-14 03:50:17 +08:00
2b29b432d2
This is part two of the change started in r359330. This patch moves the ownership of the script interpreter from the command interpreter into the debugger. I would've preferred to remove the lazy initialization, however the fact that the scripting language is set after the debugger is created makes that tricky. So for now this does exactly the same thing as when it was under the command interpreter. The result is that this patch is fully NFC. Differential revision: https://reviews.llvm.org/D61211 llvm-svn: 359354
80 lines
2.7 KiB
C++
80 lines
2.7 KiB
C++
//===-- CommandObjectScript.cpp ---------------------------------*- C++ -*-===//
|
|
//
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#include "CommandObjectScript.h"
|
|
|
|
|
|
#include "lldb/Core/Debugger.h"
|
|
|
|
#include "lldb/DataFormatters/DataVisualization.h"
|
|
|
|
#include "lldb/Interpreter/CommandInterpreter.h"
|
|
#include "lldb/Interpreter/CommandReturnObject.h"
|
|
#include "lldb/Interpreter/ScriptInterpreter.h"
|
|
#include "lldb/Utility/Args.h"
|
|
|
|
using namespace lldb;
|
|
using namespace lldb_private;
|
|
|
|
// CommandObjectScript
|
|
|
|
CommandObjectScript::CommandObjectScript(CommandInterpreter &interpreter,
|
|
ScriptLanguage script_lang)
|
|
: CommandObjectRaw(
|
|
interpreter, "script",
|
|
"Invoke the script interpreter with provided code and display any "
|
|
"results. Start the interactive interpreter if no code is supplied.",
|
|
"script [<script-code>]") {}
|
|
|
|
CommandObjectScript::~CommandObjectScript() {}
|
|
|
|
bool CommandObjectScript::DoExecute(llvm::StringRef command,
|
|
CommandReturnObject &result) {
|
|
#ifdef LLDB_DISABLE_PYTHON
|
|
// if we ever support languages other than Python this simple #ifdef won't
|
|
// work
|
|
result.AppendError("your copy of LLDB does not support scripting.");
|
|
result.SetStatus(eReturnStatusFailed);
|
|
return false;
|
|
#else
|
|
if (m_interpreter.GetDebugger().GetScriptLanguage() ==
|
|
lldb::eScriptLanguageNone) {
|
|
result.AppendError(
|
|
"the script-lang setting is set to none - scripting not available");
|
|
result.SetStatus(eReturnStatusFailed);
|
|
return false;
|
|
}
|
|
|
|
ScriptInterpreter *script_interpreter = GetDebugger().GetScriptInterpreter();
|
|
|
|
if (script_interpreter == nullptr) {
|
|
result.AppendError("no script interpreter");
|
|
result.SetStatus(eReturnStatusFailed);
|
|
return false;
|
|
}
|
|
|
|
DataVisualization::ForceUpdate(); // script might change Python code we use
|
|
// for formatting.. make sure we keep up to
|
|
// date with it
|
|
|
|
if (command.empty()) {
|
|
script_interpreter->ExecuteInterpreterLoop();
|
|
result.SetStatus(eReturnStatusSuccessFinishNoResult);
|
|
return result.Succeeded();
|
|
}
|
|
|
|
// We can do better when reporting the status of one-liner script execution.
|
|
if (script_interpreter->ExecuteOneLine(command, &result))
|
|
result.SetStatus(eReturnStatusSuccessFinishNoResult);
|
|
else
|
|
result.SetStatus(eReturnStatusFailed);
|
|
|
|
return result.Succeeded();
|
|
#endif
|
|
}
|