From: Juan Hoyos Date: Fri, 12 Mar 2021 08:02:00 +0000 (-0800) Subject: Change references from master to main (#2075) X-Git-Tag: submit/tizen/20210909.063632~17^2~78 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=844567b827256eb1796fd19f71becf748e8a5eeb;p=platform%2Fcore%2Fdotnet%2Fdiagnostics.git Change references from master to main (#2075) --- diff --git a/README.md b/README.md index a2c3c4966..5926f10b5 100644 --- a/README.md +++ b/README.md @@ -42,7 +42,7 @@ To install the platform's prerequisites and build: * [FAQ](documentation/FAQ.md) - Frequently asked questions. * [The LLDB Debugger](http://lldb.llvm.org/index.html) - More information about lldb. * [SOS](https://msdn.microsoft.com/en-us/library/bb190764(v=vs.110).aspx) - More information about SOS. -* [Debugging CoreCLR](https://github.com/dotnet/runtime/blob/master/docs/workflow/debugging/coreclr/debugging.md) - Instructions for debugging .NET Core and the CoreCLR runtime. +* [Debugging CoreCLR](https://github.com/dotnet/runtime/blob/main/docs/workflow/debugging/coreclr/debugging.md) - Instructions for debugging .NET Core and the CoreCLR runtime. * [dotnet/runtime](https://github.com/dotnet/runtime) - Source for the .NET Core runtime. * [Official Build Instructions](documentation/building/official-build-instructions.md) - Internal official build instructions. @@ -50,7 +50,7 @@ To install the platform's prerequisites and build: ## Build Status -[![Build Status](https://dnceng.visualstudio.com/public/_apis/build/status/dotnet/diagnostics/diagnostics-public-ci?branchName=master)](https://dnceng.visualstudio.com/public/_build/latest?definitionId=72&branchName=master) +[![Build Status](https://dnceng.visualstudio.com/public/_apis/build/status/dotnet/diagnostics/diagnostics-public-ci?branchName=main)](https://dnceng.visualstudio.com/public/_build/latest?definitionId=72&branchName=main) [//]: # (End current test results) diff --git a/diagnostics.yml b/diagnostics.yml index da9cb93a4..cbd311234 100644 --- a/diagnostics.yml +++ b/diagnostics.yml @@ -24,7 +24,6 @@ pr: autoCancel: true branches: include: - - master - main - release/* paths: diff --git a/documentation/FAQ.md b/documentation/FAQ.md index ad788a0ae..bc42c7d91 100644 --- a/documentation/FAQ.md +++ b/documentation/FAQ.md @@ -51,4 +51,4 @@ Frequently Asked Questions SOS does not support the current target architecture 'arm32' (0x01c4). A 32 bit target may require a 32 bit debugger or vice versa. In general, try to use the same bitness for the debugger and target process. ``` - You may need a different bitness of the Windows (windbg/cdb) debugger or dotnet-dump. If you are running an x64 (64 bit), try an x86 (32 bit) version. The easiest way to get an x86 version of dotnet-dump is installing the "single-file" version [here](https://aka.ms/dotnet-dump/win-x86). For more information on single-file tools see [here](https://github.com/dotnet/diagnostics/blob/master/documentation/single-file-tools.md#single-file-diagnostic-tools). + You may need a different bitness of the Windows (windbg/cdb) debugger or dotnet-dump. If you are running an x64 (64 bit), try an x86 (32 bit) version. The easiest way to get an x86 version of dotnet-dump is installing the "single-file" version [here](https://aka.ms/dotnet-dump/win-x86). For more information on single-file tools see [here](https://github.com/dotnet/diagnostics/blob/main/documentation/single-file-tools.md#single-file-diagnostic-tools). diff --git a/documentation/building/linux-instructions.md b/documentation/building/linux-instructions.md index ef7b1fca8..31e987c01 100644 --- a/documentation/building/linux-instructions.md +++ b/documentation/building/linux-instructions.md @@ -8,7 +8,7 @@ Toolchain Setup The following instructions will install the required packages. This only needs to be done once per machine. These instructions assume that you already have "sudo" installed. It is also recommended to create a github fork of the diagnostics repo and cloning that instead of https://github.com/dotnet/diagnostics.git directly. -To build or cross build for ARM on Windows or Linux see the instructions [here](https://github.com/dotnet/runtime/blob/master/docs/workflow/building/coreclr/cross-building.md#generating-the-rootfs) in the runtime repo. You will need to clone the runtime [repo](https://github.com/dotnet/runtime.git) and build the appropriate "rootfs" for arm or arm64 using these instructions. You only need to do this once. +To build or cross build for ARM on Windows or Linux see the instructions [here](https://github.com/dotnet/runtime/blob/main/docs/workflow/building/coreclr/cross-building.md#generating-the-rootfs) in the runtime repo. You will need to clone the runtime [repo](https://github.com/dotnet/runtime.git) and build the appropriate "rootfs" for arm or arm64 using these instructions. You only need to do this once. #### Ubuntu 14.04 #### diff --git a/documentation/building/official-build-instructions.md b/documentation/building/official-build-instructions.md index b0cec4ea4..a21343b0f 100644 --- a/documentation/building/official-build-instructions.md +++ b/documentation/building/official-build-instructions.md @@ -16,7 +16,7 @@ This signs and publishes the following packages to the tools feed (https://pkgs. To release the latest tools: -1) Merge all the commits for this release from the master branch to the release/stable branch. +1) Merge all the commits for this release from the main branch to the release/stable branch. 2) Kick off an official build from the release/stable branch. 3) Change all the package version references in the documentation folder to this official build's package version to maintain the docs up to date. 4) Download the above packages from the successful official build under "Artifacts" -> "PackageArtifacts". diff --git a/documentation/debugging-coredump.md b/documentation/debugging-coredump.md index 6e3a66ab2..1fc9699f9 100644 --- a/documentation/debugging-coredump.md +++ b/documentation/debugging-coredump.md @@ -1,7 +1,7 @@ Debugging Linux or MacOS Core Dump ================================== -These instructions will lead you through getting symbols, loading and debugging a Linux or MacOS core dump. The best way to generate a core dump on Linux (only) is through the [createdump](https://github.com/dotnet/runtime/blob/master/docs/design/coreclr/botr/xplat-minidump-generation.md#configurationpolicy) facility. +These instructions will lead you through getting symbols, loading and debugging a Linux or MacOS core dump. The best way to generate a core dump on Linux (only) is through the [createdump](https://github.com/dotnet/runtime/blob/main/docs/design/coreclr/botr/xplat-minidump-generation.md#configurationpolicy) facility. Dumps created with gdb or gcore do not have all the managed state so various SOS or dotnet-dump commands may display "UNKNOWN" for type and function names. This can also happen with Linux system generated core dumps if the `coredump_filter` for the process is not set to at least 0x3f. See [core](http://man7.org/linux/man-pages/man5/core.5.html) for more information. @@ -9,7 +9,7 @@ Dumps created with gdb or gcore do not have all the managed state so various SOS Because SOS now has symbol download support (both managed PDBs and native symbols via `loadsymbols`) all that lldb requires is the host program and a few other binaries. The host is usually `dotnet` but for self-contained applications it the .NET Core `apphost` renamed to the program/project name. These steps will handle either case and download the host lldb needs to properly diagnose a core dump. There are also cases that the runtime module (i.e. libcoreclr.so) is need by lldb. -First install or update the dotnet CLI symbol tool. This only needs to be done once. See this [link](https://github.com/dotnet/symstore/tree/master/src/dotnet-symbol#install) for more details. We need version 1.0.142101 or greater of dotnet-symbol installed. +First install or update the dotnet CLI symbol tool. This only needs to be done once. See this [link](https://github.com/dotnet/symstore/tree/main/src/dotnet-symbol#install) for more details. We need version 1.0.142101 or greater of dotnet-symbol installed. ~$ dotnet tool install -g dotnet-symbol You can invoke the tool using the following command: dotnet-symbol diff --git a/documentation/design-docs/diagnostics-client-library.md b/documentation/design-docs/diagnostics-client-library.md index 72c72dc96..842035ba6 100644 --- a/documentation/design-docs/diagnostics-client-library.md +++ b/documentation/design-docs/diagnostics-client-library.md @@ -1,9 +1,9 @@ # Diagnostics Client Library API Design ## Intro -The Diagnostics Client Library (currently named as "Runtime Client Library") - `Microsoft.Diagnostics.NetCore.Client.dll` - is a managed library that can be used to interact with the .NET runtime via the diagnostics IPC protocol as documented in https://github.com/dotnet/diagnostics/blob/master/documentation/design-docs/ipc-protocol.md. It provides managed classes for invoking the diagnostics IPC commands programmatically, and can be extended to write various diagnostics tools. It also comes with various classes that should facilitate interacting with the diagnostics IPC commands. +The Diagnostics Client Library (currently named as "Runtime Client Library") - `Microsoft.Diagnostics.NetCore.Client.dll` - is a managed library that can be used to interact with the .NET runtime via the diagnostics IPC protocol as documented in https://github.com/dotnet/diagnostics/blob/main/documentation/design-docs/ipc-protocol.md. It provides managed classes for invoking the diagnostics IPC commands programmatically, and can be extended to write various diagnostics tools. It also comes with various classes that should facilitate interacting with the diagnostics IPC commands. -The name "Diagnostics Client Library" comes from the fact that we call the runtime (CoreCLR) component responsible for accepting and handling the diagnostics IPC commands the "diagnostics server" - https://github.com/dotnet/runtime/blob/master/src/coreclr/src/vm/diagnosticserver.h. Since this library is a managed library on the other side of the IPC protocol responsible for communicating with the runtime's "diagnostics server", calling this the "Diagnostics Client Library" made sense. +The name "Diagnostics Client Library" comes from the fact that we call the runtime (CoreCLR) component responsible for accepting and handling the diagnostics IPC commands the "diagnostics server" - https://github.com/dotnet/runtime/blob/main/src/coreclr/vm/diagnosticserver.h. Since this library is a managed library on the other side of the IPC protocol responsible for communicating with the runtime's "diagnostics server", calling this the "Diagnostics Client Library" made sense. ## Goals @@ -243,7 +243,7 @@ public static int AttachProfiler(int processId, Guid profilerGuid, string profil ## API Descriptions -At a high level, the DiagnosticsClient class provides static methods that the user may call to invoke diagnostics IPC commands (i.e. start an EventPipe session, request a core dump, etc.) The library also provides several classes that may be helpful for invoking these commands. These commands are described in more detail in the diagnostics IPC protocol documentation available here: https://github.com/dotnet/diagnostics/blob/master/documentation/design-docs/ipc-protocol.md#commands. +At a high level, the DiagnosticsClient class provides static methods that the user may call to invoke diagnostics IPC commands (i.e. start an EventPipe session, request a core dump, etc.) The library also provides several classes that may be helpful for invoking these commands. These commands are described in more detail in the diagnostics IPC protocol documentation available here: https://github.com/dotnet/diagnostics/blob/main/documentation/design-docs/ipc-protocol.md#commands. ### DiagnosticsClient @@ -381,4 +381,3 @@ namespace Microsoft.Diagnostics.NETCore.Client } } ``` - diff --git a/documentation/design-docs/dotnet-tools.md b/documentation/design-docs/dotnet-tools.md index b66b5879d..8cf898253 100644 --- a/documentation/design-docs/dotnet-tools.md +++ b/documentation/design-docs/dotnet-tools.md @@ -199,7 +199,7 @@ MONITOR CPU Usage (%) 24 GC Heap Size (MB) 811 - 3. Monitoring EventCounter values from user-defined EventSource: (see https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.Tracing/documentation/EventCounterTutorial.md on how to do this.0) + 3. Monitoring EventCounter values from user-defined EventSource: (see https://github.com/dotnet/corefx/blob/main/src/System.Diagnostics.Tracing/documentation/EventCounterTutorial.md on how to do this.0) > dotnet-counters monitor --processId 1902 Samples-EventCounterDemos-Minimal @@ -1197,7 +1197,7 @@ perf top monitors a machine and shows an updating console UI with the most expen ### Pprof -Pprof is both a runtime library used by golang to collect trace data as well as a CLI tool to visualize that data after it has been collected. The CLI tool is the focus here. Snippets below from https://github.com/google/pprof/blob/master/doc/README.md +Pprof is both a runtime library used by golang to collect trace data as well as a CLI tool to visualize that data after it has been collected. The CLI tool is the focus here. Snippets below from https://github.com/google/pprof/blob/main/doc/README.md Pprof follows the convention Pprof [options] source. diff --git a/documentation/design-docs/eventcounters.md b/documentation/design-docs/eventcounters.md index e62b9d361..2815eca2c 100644 --- a/documentation/design-docs/eventcounters.md +++ b/documentation/design-docs/eventcounters.md @@ -157,7 +157,7 @@ IncrementingPollingCounter monitorContentionCounter = new IncrementingPollingCou This counter uses the [Monitor.LockContentionCount](https://docs.microsoft.com/en-us/dotnet/api/system.threading.monitor.lockcontentioncount?view=netcore-3.0) API to report the increment of the total lock contention count. The `DisplayRateTimeScale` property is an optional `TimeSpan` which can be set to provide a hint of what time interval this counter is best displayed at. For example, the lock contention count is best displayed as *count per second*, so its `DisplayRateTimeScale` is set to 1 second. This can be adjusted for different types of rate counters. -There are more runtime counter implementation to use as a reference in the [CoreCLR](https://github.com/dotnet/runtime/blob/master/src/coreclr/src/System.Private.CoreLib/src/System/Diagnostics/Eventing/RuntimeEventSource.cs) repo. +There are more runtime counter implementation to use as a reference in the [CoreCLR](https://github.com/dotnet/runtime/blob/main/src/coreclr/System.Private.CoreLib/src/System/Diagnostics/Eventing/RuntimeEventSource.cs) repo. ## Concurrency It is important to note that if the delegates passed to the `PollingCounter`/`IncrementingPollingCounter` instances are called by multiple threads at once, the EventCounters API does not guarantee thread safety. It is the author's responsibility to guarantee the thread-safety of the delegates being passed to the counter APIs. @@ -303,7 +303,7 @@ Consuming EventCounters out-of-proc is also possible. For those that are familia #### dotnet-counters -dotnet-counters is a cross-platform dotnet CLI tool that can be used to monitor the counter values. To find out how to use `dotnet-counters` to monitor your counters, refer to the [dotnet-counters documentation](https://github.com/dotnet/diagnostics/blob/master/documentation/dotnet-counters-instructions.md). +dotnet-counters is a cross-platform dotnet CLI tool that can be used to monitor the counter values. To find out how to use `dotnet-counters` to monitor your counters, refer to the [dotnet-counters documentation](https://github.com/dotnet/diagnostics/blob/main/documentation/dotnet-counters-instructions.md). #### ETW/PerfView @@ -325,11 +325,11 @@ Here is an example of using dotnet-trace to get the same counter data. dotnet-trace collect --process-id --providers Samples-EventCounterDemos-Minimal:0:0:EventCounterIntervalSec=1 ``` -The official dotnet-trace documentation contains a [section](https://github.com/dotnet/diagnostics/blob/master/documentation/dotnet-trace-instructions.md#using-dotnet-trace-to-collect-counter-values-over-time) on how to do this in more detail. +The official dotnet-trace documentation contains a [section](https://github.com/dotnet/diagnostics/blob/main/documentation/dotnet-trace-instructions.md#using-dotnet-trace-to-collect-counter-values-over-time) on how to do this in more detail. #### TraceEvent -TraceEvent is a managed library that makes it easy to consume ETW and EventPipe events. For more information, refer to the [TraceEvent Library Programmers Guide](https://github.com/Microsoft/perfview/blob/master/documentation/TraceEvent/TraceEventProgrammersGuide.md). +TraceEvent is a managed library that makes it easy to consume ETW and EventPipe events. For more information, refer to the [TraceEvent Library Programmers Guide](https://github.com/Microsoft/perfview/blob/main/documentation/TraceEvent/TraceEventProgrammersGuide.md). For some more detailed code samples, you can also try reading [Criteo Labs blog](https://medium.com/criteo-labs/net-core-counters-internals-how-to-integrate-counters-in-your-monitoring-pipeline-5354cd61b42e) on how to do this. \ No newline at end of file diff --git a/documentation/diagnostics-planing.md b/documentation/diagnostics-planing.md index bd7a1d8e3..c8434192d 100644 --- a/documentation/diagnostics-planing.md +++ b/documentation/diagnostics-planing.md @@ -1,6 +1,6 @@ # .NET Core Diagnostics Vision -[This document](https://github.com/dotnet/diagnostics/blob/master/documentation/diagnostics-planing.md) +[This document](https://github.com/dotnet/diagnostics/blob/main/documentation/diagnostics-planing.md) describes a high level vision/plan for diagnostics / monitoring for the .NET Core runtime. The overarching goal is easy to state. @@ -360,7 +360,7 @@ A high level summary of the work being done is as follows Then flesh that out with details on how to do specific investigations, and in particular all the other work items listed here will be included in that documentation. 2. Add a new DumpASync command to the SOS debugging extension. Work with Visual Studio Team to have it integrated into their parallel stacks view. Make sure our existing Async diagnostics works well. - 3. Create a new 'dotnet-collect' global command that allows the collection of EventPipe data 'by hand'. (See [dotnet-collect And dotnet-analyze](https://github.com/aspnet/AspLabs/tree/master/src/DotNetDiagnostics) for more. + 3. Create a new 'dotnet-collect' global command that allows the collection of EventPipe data 'by hand'. (See [dotnet-collect And dotnet-analyze](https://github.com/aspnet/AspLabs/tree/main/src/DotNetDiagnostics) for more. It should be able to collect traces that can be read with either PerfView or Visual Studio. 4. Create a new 'dotnet-analyze' global command that allows you to do investigations on crash dumps. Simple triage of crashes as well as memory investigations should be possible. 5. Insure that normal Azure and App-Insights default dashboard metrics work with .NET Core (on all platforms). dotnet-collect will allow the ad-hoc collection of metrics for local monitoring. diff --git a/documentation/dotnet-counters-instructions.md b/documentation/dotnet-counters-instructions.md index 32feb22cd..4faf0868b 100644 --- a/documentation/dotnet-counters-instructions.md +++ b/documentation/dotnet-counters-instructions.md @@ -99,7 +99,7 @@ dotnet tool install --global dotnet-counters GC Heap Size (MB) 811 Number of Exceptions / sec 4 - 3. Monitoring EventCounter values from user-defined EventSource: (see https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.Tracing/documentation/EventCounterTutorial.md on how to do this.0) + 3. Monitoring EventCounter values from user-defined EventSource: (see https://github.com/dotnet/corefx/blob/main/src/System.Diagnostics.Tracing/documentation/EventCounterTutorial.md on how to do this.0) > dotnet-counters monitor --process-id 1902 Samples-EventCounterDemos-Minimal diff --git a/documentation/dotnet-dump-instructions.md b/documentation/dotnet-dump-instructions.md index 71a6af951..5043e8e35 100644 --- a/documentation/dotnet-dump-instructions.md +++ b/documentation/dotnet-dump-instructions.md @@ -33,7 +33,7 @@ If this is the first global tool installed or you get message `Could not execute ## Using dotnet-dump -The next step is to collect a dump. This can be skipped if a core dump has already been generated by the operating system or [createdump](https://github.com/dotnet/runtime/blob/master/docs/design/coreclr/botr/xplat-minidump-generation.md#configurationpolicy) on Linux. The default dump type (--type option) is currently "full". +The next step is to collect a dump. This can be skipped if a core dump has already been generated by the operating system or [createdump](https://github.com/dotnet/runtime/blob/main/docs/design/coreclr/botr/xplat-minidump-generation.md#configurationpolicy) on Linux. The default dump type (--type option) is currently "full". On Linux, the .NET runtime version must be 3.0 or greater. On Windows, `dotnet-dump collect` will work with any version of the .NET runtime. diff --git a/documentation/dotnet-trace-instructions.md b/documentation/dotnet-trace-instructions.md index 924b844b0..d04a2ac35 100644 --- a/documentation/dotnet-trace-instructions.md +++ b/documentation/dotnet-trace-instructions.md @@ -156,7 +156,7 @@ Monitoring | 200000000 | Events intended for monito Codesymbols | 400000000 | Events that will dump PDBs of dynamically generated assemblies to the EventPipe stream. Default | 4C14FCCBD | Recommend default flags (good compromise on verbosity). -[source](https://github.com/Microsoft/perfview/blob/master/src/TraceEvent/Parsers/ClrTraceEventParser.cs#L41) +[source](https://github.com/Microsoft/perfview/blob/main/src/TraceEvent/Parsers/ClrTraceEventParser.cs#L41) ## More information on .NET Providers diff --git a/documentation/privatebuildtesting.md b/documentation/privatebuildtesting.md index 4750c8c23..25fcaa656 100644 --- a/documentation/privatebuildtesting.md +++ b/documentation/privatebuildtesting.md @@ -3,7 +3,7 @@ Private runtime build testing Here are some instructions on how to run the diagnostics repo's tests against a locally build private .NET Core runtime. These directions will work on Windows, Linux and MacOS. -1. Build the runtime repo (see [Workflow Guide](https://github.com/dotnet/runtime/blob/master/docs/workflow/README.md)). +1. Build the runtime repo (see [Workflow Guide](https://github.com/dotnet/runtime/blob/main/docs/workflow/README.md)). 2. Build the diagnostics repo (see [Building the Repository](../README.md)). 3. Run the diagnostics repo tests with the -privatebuildpath option. @@ -24,7 +24,7 @@ On Linux/MacOS: ``` ~/diagnostics$ ./test.sh --privatebuildpath /home/user/runtime/artifacts/bin/coreclr/Linux.x64.Debug ``` -The private runtime will be copied to the diagnostics repo and the tests started. It can be just the runtime binaries but this assumes that the private build is close to the latest published master build. If not, you can pass the runtime's testhost directory containing all the shared runtime bits i.e. `c:\runtime\artifacts\bin\coreclr\testhost\netcoreapp5.0-Windows_NT-Debug-x64\shared\Microsoft.NETCore.App\5.0.0` or `/home/user/runtime/artifacts/bin/coreclr/testhost/netcoreapp5.0-Linux-Release-x64/shared/Microsoft.NETCore.App/5.0.0` +The private runtime will be copied to the diagnostics repo and the tests started. It can be just the runtime binaries but this assumes that the private build is close to the latest published main build. If not, you can pass the runtime's testhost directory containing all the shared runtime bits i.e. `c:\runtime\artifacts\bin\coreclr\testhost\netcoreapp5.0-Windows_NT-Debug-x64\shared\Microsoft.NETCore.App\5.0.0` or `/home/user/runtime/artifacts/bin/coreclr/testhost/netcoreapp5.0-Linux-Release-x64/shared/Microsoft.NETCore.App/5.0.0` On Linux/MacOS it is recommended to test against Release runtime builds because of a benign assert in DAC (tracked by issue #[31897](https://github.com/dotnet/runtime/issues/31897)) that causes the tests to fail. diff --git a/documentation/tutorial/app_is_leaking_memory_eventual_crash.md b/documentation/tutorial/app_is_leaking_memory_eventual_crash.md index f08023f17..dc29ecf6f 100644 --- a/documentation/tutorial/app_is_leaking_memory_eventual_crash.md +++ b/documentation/tutorial/app_is_leaking_memory_eventual_crash.md @@ -56,7 +56,7 @@ Now that we have a core dump generated, what options do we have to analyze the c In both cases, you have to be careful to roughly match the environment up with the production server. For example, if I am running .net core preview 5 on Ubuntu 16.04 the core dump must be analyzed on the same architecture and environment. -For the LLDB/SOS experience, please see - https://github.com/dotnet/runtime/blob/master/docs/workflow/building/coreclr/debugging-instructions.md. +For the LLDB/SOS experience, please see - https://github.com/dotnet/runtime/blob/main/docs/workflow/building/coreclr/debugging-instructions.md. To use the dotnet-dump tool to analyze the dump please run: diff --git a/documentation/tutorial/hung_app.md b/documentation/tutorial/hung_app.md index d9e541775..52a8928ed 100644 --- a/documentation/tutorial/hung_app.md +++ b/documentation/tutorial/hung_app.md @@ -270,7 +270,7 @@ One of the pain points in our analysis process was around having to eye ball hun Before we get started, you need to do the following: 1. Clone the dotnet/diagnostics repo (https://github.com/dotnet/diagnostics) -2. Make sure all the pre-requisites are in place to build the repo (https://github.com/dotnet/diagnostics/blob/master/README.md) +2. Make sure all the pre-requisites are in place to build the repo (https://github.com/dotnet/diagnostics/blob/main/README.md) 3. Add the uniquestacks.cs file to ~/diagnostics/src/Tools/dotnet-dump/Commands folder. 4. Build the repo using ~/diagnostics/build.sh diff --git a/documentation/using-sos-private-build.md b/documentation/using-sos-private-build.md index 32842992f..d27aad21f 100644 --- a/documentation/using-sos-private-build.md +++ b/documentation/using-sos-private-build.md @@ -2,7 +2,7 @@ This document is written for people who need to use the bleeding edge SOS freshly built from the enlistment. You may need to do it because you want the latest feature, or you are developing your own SOS command and you want to try it out. Regardless of the reason, here is how you can do it. -Before we can use the private build, of course, we must build it first. [Here](https://github.com/dotnet/diagnostics/tree/master/documentation/building) is the documentation on how to do that. +Before we can use the private build, of course, we must build it first. [Here](https://github.com/dotnet/diagnostics/tree/main/documentation/building) is the documentation on how to do that. ## Windows @@ -30,4 +30,3 @@ On Linux, we have to manually load `libsosplugin.so`, so we can simply load it f ``` Then we are using our own sos and we can do whatever we want with it! - diff --git a/eng/clang-compiler-override-arm.txt b/eng/clang-compiler-override-arm.txt index 5b6f54667..f02ced268 100644 --- a/eng/clang-compiler-override-arm.txt +++ b/eng/clang-compiler-override-arm.txt @@ -2,7 +2,7 @@ SET (CMAKE_C_FLAGS_INIT "-Wall -std=c11") SET (CMAKE_C_FLAGS_DEBUG_INIT "-g -O0") SET (CLR_C_FLAGS_CHECKED_INIT "-g -O1") # Refer to the below instruction to support __thread with -O2/-O3 on Linux/ARM -# https://github.com/dotnet/runtime/blob/master/docs/workflow/building/coreclr/linux-instructions.md +# https://github.com/dotnet/runtime/blob/main/docs/workflow/building/coreclr/linux-instructions.md SET (CMAKE_C_FLAGS_RELEASE_INIT "-g -O1") SET (CMAKE_C_FLAGS_RELWITHDEBINFO_INIT "-g -O1") diff --git a/eng/clang-compiler-override.txt b/eng/clang-compiler-override.txt index 0a68fba52..2741303b8 100644 --- a/eng/clang-compiler-override.txt +++ b/eng/clang-compiler-override.txt @@ -2,7 +2,7 @@ SET (CMAKE_C_FLAGS_INIT "-Wall -std=c11") SET (CMAKE_C_FLAGS_DEBUG_INIT "-g -O0") SET (CLR_C_FLAGS_CHECKED_INIT "-g -O2") # Refer to the below instruction to support __thread with -O2/-O3 on Linux/ARM -# https://github.com/dotnet/runtime/blob/master/docs/workflow/building/coreclr/linux-instructions.md +# https://github.com/dotnet/runtime/blob/main/docs/workflow/building/coreclr/linux-instructions.md SET (CMAKE_C_FLAGS_RELEASE_INIT "-g -O3") SET (CMAKE_C_FLAGS_RELWITHDEBINFO_INIT "-g -O2") diff --git a/eng/setup-vs-tools.cmd b/eng/setup-vs-tools.cmd index 3ad7761fd..c5edf5f79 100644 --- a/eng/setup-vs-tools.cmd +++ b/eng/setup-vs-tools.cmd @@ -31,7 +31,7 @@ echo Visual Studio 2017 or later not found :call_vs if not exist "%_VSCOMNTOOLS%" ( echo %__MsgPrefix%Error: Visual Studio 2017 or 2019 required. - echo Please see https://github.com/dotnet/runtime/blob/master/docs/workflow/building/coreclr/windows-instructions.md for build instructions. + echo Please see https://github.com/dotnet/runtime/blob/main/docs/workflow/building/coreclr/windows-instructions.md for build instructions. exit /b 1 ) echo %__MsgPrefix%"%_VSCOMNTOOLS%\VsDevCmd.bat" diff --git a/src/Microsoft.Diagnostics.ExtensionCommands/ClrMDHelper.cs b/src/Microsoft.Diagnostics.ExtensionCommands/ClrMDHelper.cs index be5f534bf..193ff2f17 100644 --- a/src/Microsoft.Diagnostics.ExtensionCommands/ClrMDHelper.cs +++ b/src/Microsoft.Diagnostics.ExtensionCommands/ClrMDHelper.cs @@ -55,7 +55,7 @@ namespace Microsoft.Diagnostics.ExtensionCommands return tks.ToString(); } - // from CLR implementation in https://github.com/dotnet/runtime/blob/master/src/libraries/System.Private.CoreLib/src/System/Threading/Tasks/Task.cs#L141 + // from CLR implementation in https://github.com/dotnet/runtime/blob/main/src/libraries/System.Private.CoreLib/src/System/Threading/Tasks/Task.cs#L141 internal const int TASK_STATE_STARTED = 0x00010000; internal const int TASK_STATE_DELEGATE_INVOKED = 0x00020000; internal const int TASK_STATE_DISPOSED = 0x00040000; diff --git a/src/Microsoft.Diagnostics.Monitoring/CommandLineHelper.cs b/src/Microsoft.Diagnostics.Monitoring/CommandLineHelper.cs index c13d6e00b..653467e84 100644 --- a/src/Microsoft.Diagnostics.Monitoring/CommandLineHelper.cs +++ b/src/Microsoft.Diagnostics.Monitoring/CommandLineHelper.cs @@ -25,7 +25,7 @@ namespace Microsoft.Diagnostics.Monitoring // Store character literals as it iterates the command line. Escaped // characters within double quotes are unescaped for non-Windows systems. // Algorithm based on INIT_FormatCommandLine behavior from - // https://github.com/dotnet/runtime/blob/master/src/coreclr/src/pal/src/init/pal.cpp + // https://github.com/dotnet/runtime/blob/main/src/coreclr/pal/src/init/pal.cpp StringBuilder builder = new StringBuilder(commandLineLength); do { diff --git a/src/SOS/SOS.Hosting/SymbolServiceWrapper.cs b/src/SOS/SOS.Hosting/SymbolServiceWrapper.cs index a01445e94..80fd5235f 100644 --- a/src/SOS/SOS.Hosting/SymbolServiceWrapper.cs +++ b/src/SOS/SOS.Hosting/SymbolServiceWrapper.cs @@ -837,7 +837,7 @@ namespace SOS.Hosting private void ReadPortableDebugTableEntries(PEReader peReader, out DebugDirectoryEntry codeViewEntry, out DebugDirectoryEntry embeddedPdbEntry) { - // See spec: https://github.com/dotnet/corefx/blob/master/src/System.Reflection.Metadata/specs/PE-COFF.md + // See spec: https://github.com/dotnet/runtime/blob/main/docs/design/specs/PE-COFF.md codeViewEntry = default; embeddedPdbEntry = default; diff --git a/src/SOS/Strike/strike.cpp b/src/SOS/Strike/strike.cpp index 2f0f0bfc9..006667b22 100644 --- a/src/SOS/Strike/strike.cpp +++ b/src/SOS/Strike/strike.cpp @@ -2389,7 +2389,7 @@ enum StackTraceElementFlags }; // This struct needs to match the definition in the runtime. -// See: https://github.com/dotnet/runtime/blob/master/src/coreclr/src/vm/clrex.h +// See: https://github.com/dotnet/runtime/blob/main/src/coreclr/vm/clrex.h struct StackTraceElement { UINT_PTR ip; @@ -2815,7 +2815,7 @@ HRESULT FormatException(CLRDATA_ADDRESS taObj, BOOL bLineNumbers = FALSE) if (arrayLen != 0 && hr == S_OK) { // This code is accessing the StackTraceInfo class in the runtime. - // See: https://github.com/dotnet/runtime/blob/master/src/coreclr/src/vm/clrex.h + // See: https://github.com/dotnet/runtime/blob/main/src/coreclr/vm/clrex.h #ifdef _TARGET_WIN64_ DWORD_PTR dataPtr = taStackTrace + sizeof(DWORD_PTR) + sizeof(DWORD) + sizeof(DWORD); #else @@ -15732,7 +15732,7 @@ HRESULT AppendExceptionInfo(CLRDATA_ADDRESS cdaObj, if (arrayLen) { // This code is accessing the StackTraceInfo class in the runtime. - // See: https://github.com/dotnet/runtime/blob/master/src/coreclr/src/vm/clrex.h + // See: https://github.com/dotnet/runtime/blob/main/src/coreclr/vm/clrex.h #ifdef _TARGET_WIN64_ DWORD_PTR dataPtr = arrayPtr + sizeof(DWORD_PTR) + sizeof(DWORD) + sizeof(DWORD); #else diff --git a/src/inc/cortypeinfo.h b/src/inc/cortypeinfo.h index 6cc732576..3953531f1 100644 --- a/src/inc/cortypeinfo.h +++ b/src/inc/cortypeinfo.h @@ -6,7 +6,7 @@ // // Note: This file gets parsed by the Mono IL Linker (https://github.com/mono/linker/) which may throw an exception during parsing. -// Specifically, this (https://github.com/mono/linker/blob/master/corebuild/integration/ILLink.Tasks/CreateRuntimeRootDescriptorFile.cs) will try to +// Specifically, this (https://github.com/mono/linker/blob/main/src/ILLink.Tasks/CreateRuntimeRootDescriptorFile.cs) will try to // parse this header, and it may throw an exception while doing that. If you edit this file and get a build failure on msbuild.exe D:\repos\coreclr\build.proj // you might want to check out the parser linked above. // diff --git a/src/inc/gcdecoder.cpp b/src/inc/gcdecoder.cpp index a9c2af235..8f951118f 100644 --- a/src/inc/gcdecoder.cpp +++ b/src/inc/gcdecoder.cpp @@ -15,7 +15,7 @@ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX // ****************************************************************************** // WARNING!!!: This code is also used by the runtime repo. -// See: https://github.com/dotnet/runtime/blob/master/src/coreclr/src/inc/gcdecoder.cpp +// See: https://github.com/dotnet/runtime/blob/main/src/coreclr/inc/gcdecoder.cpp // ****************************************************************************** #ifdef _TARGET_X86_ diff --git a/src/inc/gcdump.h b/src/inc/gcdump.h index 2850e3231..3de3cfd67 100644 --- a/src/inc/gcdump.h +++ b/src/inc/gcdump.h @@ -14,7 +14,7 @@ // ****************************************************************************** // WARNING!!!: This header is also used by the runtime repo. -// See: https://github.com/dotnet/runtime/blob/master/src/coreclr/src/inc/gcdump.h +// See: https://github.com/dotnet/runtime/blob/main/src/coreclr/inc/gcdump.h // ****************************************************************************** /*****************************************************************************/ diff --git a/src/inc/gcinfo.h b/src/inc/gcinfo.h index dff438992..00526758a 100644 --- a/src/inc/gcinfo.h +++ b/src/inc/gcinfo.h @@ -5,7 +5,7 @@ // ****************************************************************************** // WARNING!!!: This header is also used by the runtime repo. -// See: https://github.com/dotnet/runtime/blob/master/src/coreclr/src/inc/gcinfo.h +// See: https://github.com/dotnet/runtime/blob/main/src/coreclr/inc/gcinfo.h // ****************************************************************************** /*****************************************************************************/ diff --git a/src/inc/gcinfodecoder.h b/src/inc/gcinfodecoder.h index dc7797409..611e42c4b 100644 --- a/src/inc/gcinfodecoder.h +++ b/src/inc/gcinfodecoder.h @@ -10,7 +10,7 @@ // ****************************************************************************** // WARNING!!!: This header is also used by the runtime repo. -// See: https://github.com/dotnet/runtime/blob/master/src/coreclr/src/inc/gcinfodecoder.h +// See: https://github.com/dotnet/runtime/blob/main/src/coreclr/inc/gcinfodecoder.h // ****************************************************************************** #ifndef _GC_INFO_DECODER_ @@ -702,4 +702,3 @@ private: #endif // _GC_INFO_DECODER_ - diff --git a/src/inc/gcinfodumper.h b/src/inc/gcinfodumper.h index e8b3946a7..b88edcb51 100644 --- a/src/inc/gcinfodumper.h +++ b/src/inc/gcinfodumper.h @@ -10,7 +10,7 @@ // ****************************************************************************** // WARNING!!!: This header is also used by the runtime repo. -// See: https://github.com/dotnet/runtime/blob/master/src/coreclr/src/inc/gcinfodumper.h +// See: https://github.com/dotnet/runtime/blob/main/src/coreclr/inc/gcinfodumper.h // ****************************************************************************** // @@ -118,4 +118,3 @@ private: #endif // !__GCINFODUMPER_H__ - diff --git a/src/inc/gcinfotypes.h b/src/inc/gcinfotypes.h index 3fc0f455a..c8f178612 100644 --- a/src/inc/gcinfotypes.h +++ b/src/inc/gcinfotypes.h @@ -12,7 +12,7 @@ // ****************************************************************************** // WARNING!!!: This header is also used by the runtime repo. -// See: https://github.com/dotnet/runtime/blob/master/src/coreclr/src/inc/gcinfotypes.h +// See: https://github.com/dotnet/runtime/blob/main/src/coreclr/inc/gcinfotypes.h // ****************************************************************************** #define PARTIALLY_INTERRUPTIBLE_GC_SUPPORTED @@ -815,4 +815,3 @@ PORTABILITY_WARNING("Please specialize these definitions for your platform!") #endif #endif // !__GCINFOTYPES_H__ - diff --git a/src/inc/predeftlsslot.h b/src/inc/predeftlsslot.h index 8a4b641bf..43eb530a2 100644 --- a/src/inc/predeftlsslot.h +++ b/src/inc/predeftlsslot.h @@ -9,7 +9,7 @@ // ****************************************************************************** // WARNING!!!: This header is subset of -// https://github.com/dotnet/runtime/blob/master/src/coreclr/src/inc/predeftlsslot.h +// https://github.com/dotnet/runtime/blob/main/src/coreclr/inc/predeftlsslot.h // that SOS depends on. // ****************************************************************************** diff --git a/src/inc/stresslog.h b/src/inc/stresslog.h index 698bd61b0..bce5da219 100644 --- a/src/inc/stresslog.h +++ b/src/inc/stresslog.h @@ -19,8 +19,8 @@ // ****************************************************************************** // WARNING!!!: This header is also used by the runtime repo. -// See: https://github.com/dotnet/runtime/blob/master/src/coreclr/src/inc/stresslog.h -// Parser: https://github.com/dotnet/diagnostics/blob/master/src/SOS/Strike/stressLogDump.cpp +// See: https://github.com/dotnet/runtime/blob/main/src/coreclr/inc/stresslog.h +// Parser: https://github.com/dotnet/diagnostics/blob/main/src/SOS/Strike/stressLogDump.cpp // ****************************************************************************** diff --git a/src/inc/switches.h b/src/inc/switches.h index c19524f7d..d7f3189e2 100644 --- a/src/inc/switches.h +++ b/src/inc/switches.h @@ -86,7 +86,7 @@ #define ALLOW_SXS_JIT #define ALLOW_SXS_JIT_NGEN -//master switch for gc suspension not based on hijacking +//main switch for gc suspension not based on hijacking #define FEATURE_ENABLE_GCPOLL #if defined(_TARGET_X86_) diff --git a/src/inc/tls.h b/src/inc/tls.h index 1079b69a4..730dc5984 100644 --- a/src/inc/tls.h +++ b/src/inc/tls.h @@ -10,7 +10,7 @@ // ****************************************************************************** // WARNING!!!: This header is also used by the runtime repo. -// See: https://github.com/dotnet/runtime/blob/master/src/coreclr/src/inc/tls.h +// See: https://github.com/dotnet/runtime/blob/main/src/coreclr/inc/tls.h // ****************************************************************************** #ifndef __tls_h__ diff --git a/src/pal/prebuilt/idl/clrdata_i.cpp b/src/pal/prebuilt/idl/clrdata_i.cpp index f0f6742db..31b653cbc 100644 --- a/src/pal/prebuilt/idl/clrdata_i.cpp +++ b/src/pal/prebuilt/idl/clrdata_i.cpp @@ -10,7 +10,7 @@ /* File created by MIDL compiler version 8.01.0622 */ /* at Mon Jan 18 19:14:07 2038 */ -/* Compiler settings for C:/ssd/runtime/src/coreclr/src/inc/clrdata.idl: +/* Compiler settings for C:/ssd/runtime/src/coreclr/inc/clrdata.idl: Oicf, W1, Zp8, env=Win32 (32b run), target_arch=X86 8.01.0622 protocol : dce , ms_ext, c_ext, robust error checks: allocation ref bounds_check enum stub_data @@ -97,6 +97,3 @@ MIDL_DEFINE_GUID(IID, IID_ICLRDataEnumMemoryRegions,0x471c35b4,0x7c2f,0x4ef0,0xa #ifdef __cplusplus } #endif - - - diff --git a/src/pal/prebuilt/idl/sospriv_i.cpp b/src/pal/prebuilt/idl/sospriv_i.cpp index 44e6f3ca7..214e5bee2 100644 --- a/src/pal/prebuilt/idl/sospriv_i.cpp +++ b/src/pal/prebuilt/idl/sospriv_i.cpp @@ -8,7 +8,7 @@ /* File created by MIDL compiler version 8.01.0622 */ /* at Mon Jan 18 19:14:07 2038 */ -/* Compiler settings for C:/ssd/runtime/src/coreclr/src/inc/sospriv.idl: +/* Compiler settings for C:/ssd/runtime/src/coreclr/inc/sospriv.idl: Oicf, W1, Zp8, env=Win32 (32b run), target_arch=X86 8.01.0622 protocol : dce , ms_ext, c_ext, robust error checks: allocation ref bounds_check enum stub_data @@ -114,6 +114,3 @@ MIDL_DEFINE_GUID(IID, IID_ISOSDacInterface10,0x90B8FCC3,0x7251,0x4B0A,0xAE,0x3D, #ifdef __cplusplus } #endif - - - diff --git a/src/pal/prebuilt/inc/clrdata.h b/src/pal/prebuilt/inc/clrdata.h index 6d6700554..015eaf885 100644 --- a/src/pal/prebuilt/inc/clrdata.h +++ b/src/pal/prebuilt/inc/clrdata.h @@ -8,7 +8,7 @@ /* File created by MIDL compiler version 8.01.0622 */ /* at Mon Jan 18 19:14:07 2038 */ -/* Compiler settings for C:/ssd/runtime/src/coreclr/src/inc/clrdata.idl: +/* Compiler settings for C:/ssd/runtime/src/coreclr/inc/clrdata.idl: Oicf, W1, Zp8, env=Win32 (32b run), target_arch=X86 8.01.0622 protocol : dce , ms_ext, c_ext, robust error checks: allocation ref bounds_check enum stub_data @@ -1237,5 +1237,3 @@ EXTERN_C const IID IID_ICLRDataEnumMemoryRegions; #endif #endif - - diff --git a/src/pal/src/include/pal/dbgmsg.h b/src/pal/src/include/pal/dbgmsg.h index e01f58d0e..c51cc9f26 100644 --- a/src/pal/src/include/pal/dbgmsg.h +++ b/src/pal/src/include/pal/dbgmsg.h @@ -223,7 +223,7 @@ extern BOOL g_Dbg_asserts_enabled; output, because those functions do tracing and we need to avoid recursion */ extern FILE *output_file; -/* master switch for debug channel enablement, to be modified by debugger */ +/* main switch for debug channel enablement, to be modified by debugger */ extern Volatile dbg_master_switch ; @@ -530,5 +530,3 @@ void PAL_DisplayDialogFormatted(const char *szTitle, const char *szTextFormat, . #endif // __cplusplus #endif /* _PAL_DBGMSG_H_ */ - - diff --git a/src/pal/src/misc/dbgmsg.cpp b/src/pal/src/misc/dbgmsg.cpp index f130d6b24..95451850b 100644 --- a/src/pal/src/misc/dbgmsg.cpp +++ b/src/pal/src/misc/dbgmsg.cpp @@ -69,7 +69,7 @@ BOOL g_Dbg_asserts_enabled; output, because those functions do tracing and we need to avoid recursion */ FILE *output_file = NULL; -/* master switch for debug channel enablement, to be modified by debugger */ +/* main switch for debug channel enablement, to be modified by debugger */ Volatile dbg_master_switch = TRUE; diff --git a/src/tests/DacCompareNativeTypes/DwarfParse.cs b/src/tests/DacCompareNativeTypes/DwarfParse.cs index f5ce600d6..0e3ca4e13 100644 --- a/src/tests/DacCompareNativeTypes/DwarfParse.cs +++ b/src/tests/DacCompareNativeTypes/DwarfParse.cs @@ -4,9 +4,9 @@ // // Sample lines: // -// <1><0x9ad2 GOFF=0x1e17b22> DW_AT_name<"STORAGESIGNATURE"> DW_AT_byte_size<0x00000010> DW_AT_decl_file<0x00000014 /home/stmaclea/git/runtime/src/coreclr/src/md/inc/mdfileformat.h> DW_AT_decl_line<0x0000003f> -// <1><0x44 GOFF=0x1b51> DW_AT_name<"_GUID"> DW_AT_byte_size<0x00000010> DW_AT_decl_file<0x00000001 /home/stmaclea/git/runtime/src/coreclr/src/pal/inc/pal_mstypes.h> DW_AT_decl_line<0x000002ab> -// <2><0x4d GOFF=0x1b5a> DW_AT_name<"Data1"> DW_AT_type<<0x00000082 GOFF=0x00001b8f>> DW_AT_decl_file<0x00000001 /home/stmaclea/git/runtime/src/coreclr/src/pal/inc/pal_mstypes.h> DW_AT_decl_line<0x000002ac> DW_AT_data_member_location<0> +// <1><0x9ad2 GOFF=0x1e17b22> DW_AT_name<"STORAGESIGNATURE"> DW_AT_byte_size<0x00000010> DW_AT_decl_file<0x00000014 /home/stmaclea/git/runtime/src/coreclr/md/inc/mdfileformat.h> DW_AT_decl_line<0x0000003f> +// <1><0x44 GOFF=0x1b51> DW_AT_name<"_GUID"> DW_AT_byte_size<0x00000010> DW_AT_decl_file<0x00000001 /home/stmaclea/git/runtime/src/coreclr/pal/inc/pal_mstypes.h> DW_AT_decl_line<0x000002ab> +// <2><0x4d GOFF=0x1b5a> DW_AT_name<"Data1"> DW_AT_type<<0x00000082 GOFF=0x00001b8f>> DW_AT_decl_file<0x00000001 /home/stmaclea/git/runtime/src/coreclr/pal/inc/pal_mstypes.h> DW_AT_decl_line<0x000002ac> DW_AT_data_member_location<0> using System.Collections.Generic; using System.Globalization; @@ -17,10 +17,10 @@ using static ParserExtensions; class DwarfParser { static Regex typeNameRegEx = new Regex(@"^<(?\d+)><.*GOFF=0x(?[0-9a-fA-F]+)>(.*DW_AT_name<(?[^<>]*(((?'Open'<)[^<>]*)+((?'Close-Open'>)[^<>]*)+)*(?(Open)(?!)))>)?"); - // <1><0x9ad2 GOFF=0x1e17b22> DW_AT_name DW_AT_byte_size<0x00000010> DW_AT_decl_file<0x00000014 /home/stmaclea/git/runtime/src/coreclr/src/md/inc/mdfileformat.h> DW_AT_decl_line<0x0000003f> + // <1><0x9ad2 GOFF=0x1e17b22> DW_AT_name DW_AT_byte_size<0x00000010> DW_AT_decl_file<0x00000014 /home/stmaclea/git/runtime/src/coreclr/md/inc/mdfileformat.h> DW_AT_decl_line<0x0000003f> static Regex typeRegEx = new Regex(@"^<(?\d+)><.*GOFF=0x(?[0-9a-fA-F]+)>(.*DW_AT_name<(?[^<>]*(((?'Open'<)[^<>]*)+((?'Close-Open'>)[^<>]*)+)*(?(Open)(?!)))>)?.*?DW_AT_decl_file"); - // <2><0x4d GOFF=0x1b5a> DW_AT_name DW_AT_type<<0x00000082 GOFF=0x00001b8f>> DW_AT_decl_file<0x00000001 /home/stmaclea/git/runtime/src/coreclr/src/pal/inc/pal_mstypes.h> DW_AT_decl_line<0x000002ac> DW_AT_data_member_location<0> + // <2><0x4d GOFF=0x1b5a> DW_AT_name DW_AT_type<<0x00000082 GOFF=0x00001b8f>> DW_AT_decl_file<0x00000001 /home/stmaclea/git/runtime/src/coreclr/pal/inc/pal_mstypes.h> DW_AT_decl_line<0x000002ac> DW_AT_data_member_location<0> static Regex memberRegEx = new Regex(@"^<(?\d+)><.*GOFF=0x(?[0-9a-fA-F]+)>.*.*?DW_AT_data_member_location<(?\d+) *([(][^)]*[)])?>"); // DW_AT_name