b9c1b51e45
*** to conform to clang-format’s LLVM style. This kind of mass change has
*** two obvious implications:
Firstly, merging this particular commit into a downstream fork may be a huge
effort. Alternatively, it may be worth merging all changes up to this commit,
performing the same reformatting operation locally, and then discarding the
merge for this particular commit. The commands used to accomplish this
reformatting were as follows (with current working directory as the root of
the repository):
find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} +
find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ;
The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.
Secondly, “blame” style tools will generally point to this commit instead of
a meaningful prior commit. There are alternatives available that will attempt
to look through this change and find the appropriate prior commit. YMMV.
llvm-svn: 280751
69 lines
2.4 KiB
C++
69 lines
2.4 KiB
C++
//===-- ExecutionContextScope.h ---------------------------------*- C++ -*-===//
|
|
//
|
|
// The LLVM Compiler Infrastructure
|
|
//
|
|
// This file is distributed under the University of Illinois Open Source
|
|
// License. See LICENSE.TXT for details.
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#ifndef liblldb_ExecutionContextScope_h_
|
|
#define liblldb_ExecutionContextScope_h_
|
|
|
|
// C Includes
|
|
// C++ Includes
|
|
// Other libraries and framework includes
|
|
// Project includes
|
|
#include "lldb/lldb-private.h"
|
|
|
|
namespace lldb_private {
|
|
|
|
//----------------------------------------------------------------------
|
|
/// @class ExecutionContextScope ExecutionContextScope.h
|
|
/// "lldb/Symbol/ExecutionContextScope.h"
|
|
/// @brief Inherit from this if your object can reconstruct its
|
|
/// execution context.
|
|
///
|
|
/// Many objects that have pointers back to parent execution context
|
|
/// objects can inherit from this pure virtual class can reconstruct
|
|
/// their execution context without having to keep a complete
|
|
/// ExecutionContext object in the object state. Examples of these
|
|
/// objects include: Process, Thread, RegisterContext and StackFrame.
|
|
///
|
|
/// Objects can contain a valid pointer to an instance of this so they
|
|
/// can reconstruct the execution context.
|
|
///
|
|
/// Objects that adhere to this protocol can reconstruct enough of a
|
|
/// execution context to allow functions that take a execution contexts
|
|
/// to be called.
|
|
//----------------------------------------------------------------------
|
|
class ExecutionContextScope {
|
|
public:
|
|
virtual ~ExecutionContextScope() {}
|
|
|
|
virtual lldb::TargetSP CalculateTarget() = 0;
|
|
|
|
virtual lldb::ProcessSP CalculateProcess() = 0;
|
|
|
|
virtual lldb::ThreadSP CalculateThread() = 0;
|
|
|
|
virtual lldb::StackFrameSP CalculateStackFrame() = 0;
|
|
|
|
//------------------------------------------------------------------
|
|
/// Reconstruct the object's execution context into \a sc.
|
|
///
|
|
/// The object should fill in as much of the ExecutionContextScope as it
|
|
/// can so function calls that require a execution context can be made
|
|
/// for the given object.
|
|
///
|
|
/// @param[out] exe_ctx
|
|
/// A reference to an execution context object that gets filled
|
|
/// in.
|
|
//------------------------------------------------------------------
|
|
virtual void CalculateExecutionContext(ExecutionContext &exe_ctx) = 0;
|
|
};
|
|
|
|
} // namespace lldb_private
|
|
|
|
#endif // liblldb_ExecutionContextScope_h_
|