diff options
| author | Petr Onderka <gsvick@gmail.com> | 2017-07-09 20:22:58 +0200 |
|---|---|---|
| committer | Jan Kotas <jkotas@microsoft.com> | 2017-07-09 20:22:58 +0200 |
| commit | 1f57f54b9f79a356476df9ba7a043ea967980ca4 (patch) | |
| tree | 5749899ab5743848e39f71183944eebe1133e79a /Documentation/building | |
| parent | 19042a92989904d1502d1f14798ade735ee1836a (diff) | |
| download | coreclr-1f57f54b9f79a356476df9ba7a043ea967980ca4.tar.gz coreclr-1f57f54b9f79a356476df9ba7a043ea967980ca4.tar.bz2 coreclr-1f57f54b9f79a356476df9ba7a043ea967980ca4.zip | |
Note that tests don't have to be built to view JIT dumps (#12699)
Diffstat (limited to 'Documentation/building')
| -rw-r--r-- | Documentation/building/viewing-jit-dumps.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/building/viewing-jit-dumps.md b/Documentation/building/viewing-jit-dumps.md index be5f4064a5..b16b43197f 100644 --- a/Documentation/building/viewing-jit-dumps.md +++ b/Documentation/building/viewing-jit-dumps.md @@ -8,7 +8,7 @@ To make sense of the results, it is recommended you also read the [Reading a Jit The first thing we want to do is setup the .NET Core app we want to dump. Here are the steps to do this, if you don't have one ready: -* Perform a debug build of the CoreCLR repo. +* Perform a debug build of the CoreCLR repo. You don't need to build tests, so you can pass `skiptests` to the build command to make it faster. * Install the [.NET CLI 2.0 preview](https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/dogfooding.md), which we'll use to compile/publish our app. * `cd` to where you want your app to be placed, and run `dotnet new console`. * Modify your `csproj` file so that it contains a RID (runtime ID) corresponding to the OS you're using in the `<RuntimeIdentifier>` tag. For example, for Windows 10 x64 machine, the project file is: |