From 7474ac750cdd1b32793a3c5e3344022cdbe219e4 Mon Sep 17 00:00:00 2001 From: Ilona Tomkowicz Date: Wed, 24 Nov 2021 14:29:48 +0100 Subject: [PATCH 1/2] A draft of doc for describing debugger behaviour. --- docs/design/mono/debugger.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 docs/design/mono/debugger.md diff --git a/docs/design/mono/debugger.md b/docs/design/mono/debugger.md new file mode 100644 index 0000000000000..357f96c397fd8 --- /dev/null +++ b/docs/design/mono/debugger.md @@ -0,0 +1,22 @@ +# WebAssembly Debugger + +## Overview + +The details of launching a Debugger session for a Blazor WebAssembly application is described [here](https://docs.microsoft.com/en-us/aspnet/core/blazor/debug?view=aspnetcore-6.0&tabs=visual-studio). + +## Debugger Attributes +Web Assembly Debugger supports usage of following attributes: +- __System.Diagnostics.DebuggerHidden__ + + Decorating a method - results: + - Visual Studio Breakpoints: results in disabling all existing breakpoints in the method and no possibility to set new, enabled ones. + - Stepping In/Over: results in stepping over the line with method call. + - Call stack: method does not appear on the call stack, no access to method local variables is provided. + + Decorating a method with a Debugger.Break() call inside: + - Running in the Debug mode: results in pausing the program on the line with the method call. + - Stepping In/Over: results in an additional stepping need to proceed to the next line. +
+- __System.Diagnostics.DebuggerDisplay__ +- __System.Diagnostics.DebuggerTypeProxy__ +- ... \ No newline at end of file From 8845d0d1249db62bee5fc4e20a0ff4fade6d5c1e Mon Sep 17 00:00:00 2001 From: Ilona Tomkowicz Date: Wed, 24 Nov 2021 14:44:54 +0100 Subject: [PATCH 2/2] Removing spaces. --- docs/design/mono/debugger.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/design/mono/debugger.md b/docs/design/mono/debugger.md index 357f96c397fd8..3a3a2936b79eb 100644 --- a/docs/design/mono/debugger.md +++ b/docs/design/mono/debugger.md @@ -5,18 +5,17 @@ The details of launching a Debugger session for a Blazor WebAssembly application is described [here](https://docs.microsoft.com/en-us/aspnet/core/blazor/debug?view=aspnetcore-6.0&tabs=visual-studio). ## Debugger Attributes -Web Assembly Debugger supports usage of following attributes: +Web Assembly Debugger supports usage of following attributes: - __System.Diagnostics.DebuggerHidden__ - + Decorating a method - results: - - Visual Studio Breakpoints: results in disabling all existing breakpoints in the method and no possibility to set new, enabled ones. + - Visual Studio Breakpoints: results in disabling all existing breakpoints in the method and no possibility to set new,enabled ones. - Stepping In/Over: results in stepping over the line with method call. - Call stack: method does not appear on the call stack, no access to method local variables is provided. - + Decorating a method with a Debugger.Break() call inside: - Running in the Debug mode: results in pausing the program on the line with the method call. - - Stepping In/Over: results in an additional stepping need to proceed to the next line. -
+ - Stepping In/Over: results in an additional stepping need to proceed to the next line.

- __System.Diagnostics.DebuggerDisplay__ - __System.Diagnostics.DebuggerTypeProxy__ - ... \ No newline at end of file