================
@@ -56,13 +60,83 @@ struct LLDBBaseTelemetryInfo : public
llvm::telemetry::TelemetryInfo {
void serialize(llvm::telemetry::Serializer &serializer) const override;
};
+/// Describes the exit status of a debugger.
+struct ExitDescription {
+ int exit_code;
+ std::string description;
+};
+
+struct DebuggerTelemetryInfo : public LLDBBaseTelemetryInfo {
----------------
JDevlieghere wrote:
My arguments for separate events is that it's much easier to spot what's being
collected: my backend is explicitly collecting events A, B and C and ignoring
everything else. If I need to filter out fields that's a lot harder to audit.
If you want to emit that as a single event in your backend, that's totally
fine, but that's the responsibility of the back-end. I think it's much more
important that the events are meaningful semantically.
https://github.com/llvm/llvm-project/pull/127696
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
