diff options
Diffstat (limited to 'Documentation/botr/xplat-minidump-generation.md')
| -rw-r--r-- | Documentation/botr/xplat-minidump-generation.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/botr/xplat-minidump-generation.md b/Documentation/botr/xplat-minidump-generation.md index 78660b659c..03cd517a4a 100644 --- a/Documentation/botr/xplat-minidump-generation.md +++ b/Documentation/botr/xplat-minidump-generation.md @@ -62,6 +62,7 @@ Environment variables supported: -n, --normal - create minidump (default). -h, --withheap - create minidump with heap. -t, --triage - create triage minidump. + -u, --full - create full core dump. -d, --diag - enable diagnostic messages. # Testing # @@ -73,7 +74,6 @@ The test plan is to modify the SOS tests in the (still) private debuggertests re - Do we need a full memory dump option? It would not use the _DAC_ to get the memory regions but all the readable memory from the shared module list. Do we include the shared modules' code? - May need more than just the pid for decorating dump names for docker containers because I think the _pid_ is always 1. - Do we need all the memory mappings from `/proc/$pid/maps` in the PT\_LOAD sections even though the memory is not actually in the dump? They have a file offset/size of 0. Full dumps generated by the system or _gdb_ do have these un-backed regions. -- Don't know how to get the proper size/range of the non-main thread stacks. Currently uses 4 pages around the stack pointer. The main thread has a memory region in `/proc/$pid/maps`. - There is no way to get the signal number, etc. that causes the abort from the _createdump_ utility using _ptrace_ or a /proc file. It would have to be passed from CoreCLR on the command line. - Do we need the "dynamic" sections of each shared module in the core dump? It is part of the "link_map" entry enumerated when gathering the _DSO_ information. - There may be more versioning and/or build id information needed to be added to the dump. |