| Age | Commit message (Collapse) | Author |
|---|
|
S.D.Color previews
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1040694/
|
|
updating breakpoints
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/960963
|
|
|
|
Cache IsEnum checks and do more validation that a variable/expression
evaluation result is an enum before making an expensive debugger query
to find out if the type is indeed an enum type.
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1032065/
|
|
Also added caching of Scopes and implemented GetParameters()
|
|
Needed for https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1042237/
|
|
|
|
|
|
|
|
|
|
|
|
1. update the version of VSCodeDebugProtocol used
2. Update the exception request during Lauch and Attach to catch the unhandled exception as a "stopped" event
3. While handling exception, throw exception regardless of whether a breakpoint exists or not
4. In `DebuggingService`, when `NotifyCallStackChanged()` is called when conditions satisfied, subsequent calls will occur: `OnStackChanged()` -> `SetSourceCodeFrame()` -> `NotifyCurrentFrameChanged()`. Therefore adding `noNeedUpdateFrame` to prevent duplicate calls to `OnFrameChanged`
Fixes: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1000552
|
|
|
|
|
|
|
|
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/951772
|
|
I previously "fixed" this to do StepInRequest but I was wrong.
|
|
|
|
|
|
|
|
|
|
|
|
regex parsing; remove condition calculation for regular breakpoints as
the debugger already does it.
|
|
|
|
|
|
|
|
|
|
match Sdb/Cor backends
|
|
[Debugger] Implement Set Next Statement for the VsCode debugger backend
|
|
StepInRequest instead of NextRequest
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/888799
|
|
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/698194/
|
|
Mono.Debugging.Client.Breakpoint
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/824644
|
|
Fixes VSTS #802065
|
|
|
|
Fixes VSTS #801713
It was noticed while looking at this stack trace that it was possible for
protocolClient to be null when the session was disposed.
```
[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
at MonoDevelop.Debugger.VsCodeDebugProtocol.VSCodeDebuggerSession.UpdateBreakpoints () [0x00191] in /Users/vsts/agent/2.147.1/work/1/s/monodevelop/main/src/addins/MonoDevelop.Debugger.VSCodeDebugProtocol/MonoDevelop.Debugger.VsCodeDebugProtocol/VSCodeDebuggerSession.cs:388
at MonoDevelop.Debugger.VsCodeDebugProtocol.VSCodeDebuggerSession.OnUpdateBreakEvent (Mono.Debugging.Client.BreakEventInfo eventInfo) [0x0003d] in /Users/vsts/agent/2.147.1/work/1/s/monodevelop/main/src/addins/MonoDevelop.Debugger.VSCodeDebugProtocol/MonoDevelop.Debugger.VsCodeDebugProtocol/VSCodeDebuggerSession.cs:442
at Mono.Debugging.Client.DebuggerSession.UpdateBreakEvent (Mono.Debugging.Client.BreakEvent be) [0x00021] in /Users/vsts/agent/2.147.1/work/1/s/monodevelop/main/external/debugger-libs/Mono.Debugging/Mono.Debugging.Client/DebuggerSession.cs:687
at Mono.Debugging.Client.DebuggerSession+<>c__DisplayClass116_0.<OnBreakpointModified>b__0 () [0x0000d] in /Users/vsts/agent/2.147.1/work/1/s/monodevelop/main/external/debugger-libs/Mono.Debugging/Mono.Debugging.Client/DebuggerSession.cs:722
at Mono.Debugging.Client.DebuggerSession.<Dispatch>b__92_0 (System.Object <p0>) [0x00054] in /Users/vsts/agent/2.147.1/work/1/s/monodevelop/main/external/debugger-libs/Mono.Debugging/Mono.Debugging.Client/DebuggerSession.cs:300
```
|
|
|
|
re https://github.com/xamarin/md-addins/pull/4074
|
|
The old autotools build infrastructure is largely redundant,
as projects are now built with msbuild. Remove as much as can
be done easily, along with some other obsolete stuff.
|
|
|
|
NuGet's PrivateAssets="runtime" does not work, resulting in transitive
references local copying their assemblies into every project. This
works around that by filtering out all local copies that are not
explictly listed.
This also makes it much harder to accidentally introduce local copies,
which is good as local copies in general are are not desirable due to
the way that dlls are loaded by the extension system.
|
|
|
|
|
|
|
|
stopping debugging session. This logic around HasExited and use that to log/show or not log/show exceptions is taken from SoftDebugger.
|
|
using Visual Studio for Mac version 7.5.3 (build 7) on MacOS 10.13.5 Problem was that when sending breakpoints to .NET Core Debugger we used `b.Line` instead of `b.OriginalLine` difference between two appears when runtime debugger(.NET Core) sends back to us adjusted location of breakpoint(if user places breakpoint at invalid line, debugger places to closest position and sends updated line back to IDE). So what was happening was when runtime sent updated line to IDE. IDE sent new line to runtime, but runtime then updated line position to different value and we got stuck in loop of changing line. Now we always send same value, hence problem fixed.
|
|
Remove redundant information, and make more information
redundant by setting good defaults in the MD props.
This lays some groundwork for the PackageConfig migration
and eventually SDK-style project format migration.
|
|
|
|
breaks debugging - "Debugger operation failed". Synchronous operation cancelled!
Problem was that IDE sent empty/null path for breakpoint to .NET Core debug adapter which froze in that case, hence I added `!string.IsNullOrEmpty(b.Filepath)` which fixes the problem, I also added support for FunctionBreakpoints, but later figured .NET Core adapter doesn't support that yet...
|
|
|
|
* Fix `make dist`
(cherry picked from commit 7732445e89434e17ff1e0217a640d841b29d5fc9)
* Don't strip assemblies from tarballs.
It'll make distro packagers cry, but the tarballs will actually work.
(cherry picked from commit b1820981f8acced4d4b721ce44ed5860ce8fb758)
* Include case-sensitivity fix from NRefactory
* Ensure BuildVariables.cs is up to date and in `make dist` tarballs
|
