================
@@ -1044,6 +1045,92 @@ struct CompileUnit {
};
llvm::json::Value toJSON(const CompileUnit &);
+/// Provides formatting information for a stack frame.
+struct StackFrameFormat {
+ /// Displays parameters for the stack frame.
+ bool parameters = false;
+
+ /// Displays the types of parameters for the stack frame.
+ bool parameterTypes = false;
+
+ /// Displays the names of parameters for the stack frame.
+ bool parameterNames = false;
+
+ /// Displays the values of parameters for the stack frame.
+ bool parameterValues = false;
+
+ /// Displays the line number of the stack frame.
+ bool line = false;
+
+ /// Displays the module of the stack frame.
+ bool module = false;
+
+ /// Includes all stack frames, including those the debug adapter might
+ /// otherwise hide.
+ bool includeAll = false;
+};
+bool fromJSON(const llvm::json::Value &, StackFrameFormat &, llvm::json::Path);
+
+/// A Stackframe contains the source location.
+struct StackFrame {
+ enum PresentationHint : unsigned {
+ ePresentationHintNormal,
+ ePresentationHintLabel,
+ ePresentationHintSubtle,
+ };
+
+ /// An identifier for the stack frame. It must be unique across all threads.
+ /// This id can be used to retrieve the scopes of the frame with the `scopes`
+ /// request or to restart the execution of a stack frame.
+ lldb::tid_t id;
----------------
da-viper wrote:
there is `LLDB_INVALID_THREAD_ID`
https://github.com/llvm/llvm-project/pull/173226
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
