mirror of
https://github.com/Gericom/teak-llvm.git
synced 2025-06-19 03:25:54 -04:00

Summary: A *.cpp file header in LLDB (and in LLDB) should like this: ``` //===-- TestUtilities.cpp -------------------------------------------------===// ``` However in LLDB most of our source files have arbitrary changes to this format and these changes are spreading through LLDB as folks usually just use the existing source files as templates for their new files (most notably the unnecessary editor language indicator `-*- C++ -*-` is spreading and in every review someone is pointing out that this is wrong, resulting in people pointing out that this is done in the same way in other files). This patch removes most of these inconsistencies including the editor language indicators, all the different missing/additional '-' characters, files that center the file name, missing trailing `===//` (mostly caused by clang-format breaking the line). Reviewers: aprantl, espindola, jfb, shafik, JDevlieghere Reviewed By: JDevlieghere Subscribers: dexonsmith, wuzish, emaste, sdardis, nemanjai, kbarton, MaskRay, atanasyan, arphaman, jfb, abidh, jsji, JDevlieghere, usaxena95, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D73258
69 lines
2.4 KiB
C++
69 lines
2.4 KiB
C++
//===-- CommandObjectScript.cpp -------------------------------------------===//
|
|
//
|
|
// 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/Host/Config.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) {
|
|
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;
|
|
}
|
|
|
|
// Script might change Python code we use for formatting. Make sure we keep
|
|
// up to date with it.
|
|
DataVisualization::ForceUpdate();
|
|
|
|
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();
|
|
}
|