mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2025-05-15 02:16:40 +00:00
5548cb50b2
Data formatters now cache themselves. This commit provides a new formatter cache mechanism. Upon resolving a formatter (summary or synthetic), LLDB remembers the resolution for later faster retrieval. Also moved the data formatters subsystem from the core to its own group and folder for easier management, and done some code reorganization. The ObjC runtime v1 now returns a class name if asked for the dynamic type of an object. This is required for formatters caching to work with the v1 runtime. Lastly, this commit disposes of the old hack where ValueObjects had to remember whether they were queried for formatters with their static or dynamic type. Now the ValueObjectDynamicValue class works well enough that we can use its dynamic value setting for the same purpose. llvm-svn: 173728
80 lines
2.4 KiB
C++
80 lines
2.4 KiB
C++
//===-- CommandObjectScript.cpp ---------------------------------*- C++ -*-===//
|
|
//
|
|
// The LLVM Compiler Infrastructure
|
|
//
|
|
// This file is distributed under the University of Illinois Open Source
|
|
// License. See LICENSE.TXT for details.
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#include "lldb/lldb-python.h"
|
|
|
|
#include "CommandObjectScript.h"
|
|
|
|
// C Includes
|
|
// C++ Includes
|
|
// Other libraries and framework includes
|
|
// Project includes
|
|
|
|
#include "lldb/Core/Debugger.h"
|
|
|
|
#include "lldb/DataFormatters/DataVisualization.h"
|
|
|
|
#include "lldb/Interpreter/Args.h"
|
|
#include "lldb/Interpreter/CommandInterpreter.h"
|
|
#include "lldb/Interpreter/CommandReturnObject.h"
|
|
#include "lldb/Interpreter/ScriptInterpreter.h"
|
|
|
|
using namespace lldb;
|
|
using namespace lldb_private;
|
|
|
|
//-------------------------------------------------------------------------
|
|
// CommandObjectScript
|
|
//-------------------------------------------------------------------------
|
|
|
|
CommandObjectScript::CommandObjectScript (CommandInterpreter &interpreter, ScriptLanguage script_lang) :
|
|
CommandObjectRaw (interpreter,
|
|
"script",
|
|
"Pass an expression to the script interpreter for evaluation and return the results. Drop into the interactive interpreter if no expression is given.",
|
|
"script [<script-expression-for-evaluation>]")
|
|
{
|
|
}
|
|
|
|
CommandObjectScript::~CommandObjectScript ()
|
|
{
|
|
}
|
|
|
|
bool
|
|
CommandObjectScript::DoExecute
|
|
(
|
|
const char *command,
|
|
CommandReturnObject &result
|
|
)
|
|
{
|
|
ScriptInterpreter *script_interpreter = m_interpreter.GetScriptInterpreter ();
|
|
|
|
if (script_interpreter == NULL)
|
|
{
|
|
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 == NULL || command[0] == '\0')
|
|
{
|
|
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();
|
|
}
|