diff options
Diffstat (limited to 'Documentation/debugging/unix-instructions.md')
-rw-r--r-- | Documentation/debugging/unix-instructions.md | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/Documentation/debugging/unix-instructions.md b/Documentation/debugging/unix-instructions.md index 3bb0f6f810..ccfa345848 100644 --- a/Documentation/debugging/unix-instructions.md +++ b/Documentation/debugging/unix-instructions.md @@ -65,13 +65,16 @@ lldb-3.9 -O "settings set target.exec-search-paths /home/parallels/Downloads/Sys - Install [Visual Studio Code](https://code.visualstudio.com/) - Install the [C# Extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.csharp) -- Open the folder containing the source you want to debug in VS Code +- Open the folder containing the source you want to debug in VS Code - i.e., if you are debugging a test failure in System.Net.Sockets, open `corefx/src/System.Net.Sockets` - Open the debug window: `ctrl-shift-D` or click on the button on the left - Click the gear button at the top to create a launch configuration, select `.NET Core` from the selection dropdown - In the `.NET Core Launch (console)` configuration do the following - delete the `preLaunchTask` property - - set `program` to the full path to corerun in the test directory - - set `cwd` to the test directory + - set `program` to the full path to `dotnet` in the bin directory. + - something like `corefx/bin/testhost/netcoreapp-Linux-{Configuration}-{Architecture}`, plus the full path to your corefx directory. + - set `cwd` to the test bin directory. + - using the System.Net.Sockets example, it should be something like `corefx/bin/tests/System.Net.Sockets.Tests/netcoreapp-Linux-{Configuration}-{Architecture}`, plus the full path to your corefx directory. - set `args` to the command line arguments to pass to the test - something like: `[ "xunit.console.netcore.exe", "<test>.dll", "-notrait", .... ]` + - to run a specific test, you can append something like: `[ "method", "System.Net.Sockets.Tests.{ClassName}.{TestMethodName}", ...]` - Set a breakpoint and launch the debugger, inspecting variables and call stacks will now work |