Skip to content

Commit a6b18a7

Browse files
authored
clarification on minidumps docs
1 parent ac2a35d commit a6b18a7

File tree

1 file changed

+2
-2
lines changed
  • docs/platforms/native/guides/minidumps

1 file changed

+2
-2
lines changed

docs/platforms/native/guides/minidumps/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ and can later be uploaded to Sentry. A minidump typically includes:
2828
is especially relevant for stack walking.
2929
- Optionally, the process heap. By default, this is not included to keep
3030
minidumps at a reasonable size. Sentry does not read the heap so that it can
31-
be safely omitted.
31+
be safely omitted. When using Sentry SDKs, no heap memory is included in minidumps.
3232
- The crash reason and an optional memory address associated to with the crash.
3333
For example, memory access violations. In the case of assertions, the
3434
assertion message is also included in the dump.
@@ -40,7 +40,7 @@ Minidumps are memory dumps of the process at the moment it crashes. As such,
4040
they might contain sensitive information on the target system, such as
4141
environment variables, local pathnames or maybe even in-memory representations
4242
of input fields, including passwords. **Sentry does not store these memory
43-
dumps**. Once processed, they are removed immediately, and all sensitive
43+
dumps by default**. Once processed, they are removed immediately, and all sensitive
4444
information is stripped from the resulting issues.
4545

4646
</Alert>

0 commit comments

Comments
 (0)