| commit | 1bc31b3ab1f8b5404d95db1184574ed58f4e3fba | |
| author | Alexander Kyte <alkyte@microsoft.com> | |
| Mon, 15 Oct 2018 16:38:48 +0000 (15 12:38 -0400) | ||
| committer | Alexis Christoforides <alexis@thenull.net> | |
| Mon, 15 Oct 2018 17:12:50 +0000 (15 13:12 -0400) | ||
| tree | 95e2c7340c95d4e73b8425e53de5f48b146e11f2 | treesnapshot (tar.gz zip) |
| parent | aef45d547eecdce18bce7cd355004a0be91c0a23 | commitdiff |
[crash] Bump static memory for crash string to 500k
Note:
- This memory isn't accessed until we're crashing
- On any modern machine, unused static memory is lazily allocated. When
we access it, the fault will trigger the MMU to map memory for us.
- This is guaranteed to be reentrant and safe. mmap (the alternative) is
surely fairly stable on many systems, but this is not guaranteed. The
documentation pages for mmap specifically claim it as not safe in these async
contexts.
Note:
- This memory isn't accessed until we're crashing
- On any modern machine, unused static memory is lazily allocated. When
we access it, the fault will trigger the MMU to map memory for us.
- This is guaranteed to be reentrant and safe. mmap (the alternative) is
surely fairly stable on many systems, but this is not guaranteed. The
documentation pages for mmap specifically claim it as not safe in these async
contexts.
| mono/utils/mono-state.c | diffblobblamehistory |