Search results

Linux version of the debugger is larger than macOS version

Debugger

Debugger-Poachable

OmniSharp

Status: Open.

#1654 In dotnet/vscode-csharp;

· gregg-miskelly opened on Jul 21, 2017

Thread name shows <No name> although other threads have a number as a name

Debugger

Debugger-Poachable

OmniSharp

Status: Open.

#1596 In dotnet/vscode-csharp;

· isidorn opened on Jun 27, 2017

Debugger's Locals & WATCH windows doesn't show the type of JObject for a dynamic field like other types

Debugger

Debugger-Poachable

OmniSharp

Status: Open.

#1484 In dotnet/vscode-csharp;

· cateyes99 opened on May 15, 2017

Debugger: Improve error message when attempt to attach a process which has already attached by another debugger

Bug

Debugger

Debugger-Poachable

OmniSharp

Status: Open.

#1302 In dotnet/vscode-csharp;

· ClaireKang opened on Mar 9, 2017

Debugger: Async method call stack frame incorrectly

Debugger

Debugger-Poachable

OmniSharp

Status: Open.

#1138 In dotnet/vscode-csharp;

· GraceDong opened on Jan 22, 2017

CLRDBG exited unexpectedly with exit code 137 (0x89)

Debugger

Debugger-Poachable

OmniSharp

Status: Open.

#755 In dotnet/vscode-csharp;

· mayconbeserra opened on Sep 11, 2016

clrdbg expression evaluation commands are not interuptable

Debugger

Debugger-Poachable

OmniSharp

Status: Open.

#584 In dotnet/vscode-csharp;

· rajkumar42 opened on Jul 18, 2016

Default thread name is displaying "<No Name>" in call stack.

Bug

Debugger

Debugger-Poachable

Status: Open.

#361 In dotnet/vscode-csharp;

· weinand opened on May 21, 2016

clrdbg does not accept format specifiers.

Debugger

Debugger-ExpressionEvaluation

Debugger-Poachable

Feature Request

OmniSharp

Status: Open.

#327 In dotnet/vscode-csharp;

· chuckries opened on May 16, 2016