You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starts an EventPipe tracing session using an [`EventPipeSessionConfiguration`](#eventpipesessionconfiguration-class).
168
+
169
+
*`config` / `configuration` : An `EventPipeSessionConfiguration` that defines the session.
170
+
*`token` (for the async overload): The token to monitor for cancellation requests.
105
171
106
172
> [!NOTE]
107
173
> Rundown events contain payloads that may be needed for post analysis, such as resolving method names of thread samples. Unless you know you do not want this, we recommend setting `requestRundown` to true. In large applications, this may take a while.
@@ -122,7 +188,10 @@ Request a dump for post-mortem debugging of the target application. The type of
122
188
*`logDumpGeneration` : If set to `true`, the target application will write out diagnostic logs during dump generation.
Represents a helper that creates a `DiagnosticsClient` from a diagnostic port and manages the lifetime of the underlying diagnostics server connection.
508
+
509
+
*`Instance` : The `DiagnosticsClient` connected to the target runtime.
510
+
*`DisposeAsync` : Disposes the underlying server/connection asynchronously.
511
+
*`FromDiagnosticPort` : Creates a new `DiagnosticsClientConnector` from the specified diagnostic port.
*`diagnosticPort` : The diagnostic port string (for example, a listen or connect port) to connect through.
520
+
*`ct` : The token to monitor for cancellation requests.
521
+
330
522
## DumpType enum
331
523
332
524
```csharp
@@ -346,6 +538,44 @@ Represents the type of dump that can be requested.
346
538
*`Triage`: Include just the information necessary to capture stack traces for all existing traces for all existing threads in a process. Limited GC heap memory and information. Some content that is known to contain potentially sensitive information such as full module paths will be redacted. While this is intended to mitigate some cases of sensitive data exposure, there is no guarantee this redaction feature on its own is sufficient to comply with any particular law or standard regarding data privacy.
347
539
*`Full`: Include all accessible memory in the process. The raw memory data is included at the end, so that the initial structures can be mapped directly without the raw memory information. This option can result in a very large dump file.
348
540
541
+
## WriteDumpFlags enum
542
+
543
+
```csharp
544
+
publicenumWriteDumpFlags
545
+
{
546
+
None=0x00,
547
+
LoggingEnabled=0x01,
548
+
VerboseLoggingEnabled=0x02,
549
+
CrashReportEnabled=0x04
550
+
}
551
+
```
552
+
553
+
Represents additional options that can be specified when requesting a dump.
554
+
555
+
*`None` : No additional behavior.
556
+
*`LoggingEnabled` : Enable basic logging during dump generation.
557
+
*`VerboseLoggingEnabled` : Enable verbose logging during dump generation.
558
+
*`CrashReportEnabled` : Enable generation of a crash report.
559
+
560
+
## PerfMapType enum
561
+
562
+
```csharp
563
+
publicenumPerfMapType
564
+
{
565
+
None=0,
566
+
All=1,
567
+
JitDump=2,
568
+
PerfMap=3
569
+
}
570
+
```
571
+
572
+
Represents the type of perf map behavior that can be enabled.
573
+
574
+
*`None` : No perf map output.
575
+
*`All` : Enable all perf map outputs supported by the runtime.
576
+
*`JitDump` : Enable JIT dump perf map output.
577
+
*`PerfMap` : Enable traditional perf map output.
578
+
349
579
## Exceptions
350
580
351
581
Exceptions that are thrown from the library are of type `DiagnosticsClientException` or a derived type.
@@ -385,3 +615,11 @@ public class ServerErrorException : DiagnosticsClientException
0 commit comments