Skip to content

Issues: dotnet/vscode-csharp

Top Known Issues
#5736 opened Jun 8, 2023 by mikadumont
Open 4
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
9 Open 17 Closed
9 Open 17 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Linux version of the debugger is larger than macOS version Debugger Debugger-Poachable OmniSharp
#1654 opened Jul 21, 2017 by gregg-miskelly
2
Thread name shows <No name> although other threads have a number as a name Debugger Debugger-Poachable OmniSharp
#1596 opened Jun 27, 2017 by isidorn
Debugger's Locals & WATCH windows doesn't show the type of JObject for a dynamic field like other types Debugger Debugger-Poachable OmniSharp
#1484 opened May 15, 2017 by cateyes99
2
Debugger: Improve error message when attempt to attach a process which has already attached by another debugger Bug Debugger Debugger-Poachable OmniSharp
#1302 opened Mar 9, 2017 by ClaireKang
Debugger: Async method call stack frame incorrectly Debugger Debugger-Poachable OmniSharp
#1138 opened Jan 22, 2017 by GraceDong
2
CLRDBG exited unexpectedly with exit code 137 (0x89) Debugger Debugger-Poachable OmniSharp
#755 opened Sep 11, 2016 by mayconbeserra
11
clrdbg expression evaluation commands are not interuptable Debugger Debugger-Poachable OmniSharp
#584 opened Jul 18, 2016 by rajkumar42
1
Default thread name is displaying "<No Name>" in call stack. Bug Debugger Debugger-Poachable
#361 opened May 21, 2016 by weinand
@rajkumar42
clrdbg does not accept format specifiers. Debugger Debugger-ExpressionEvaluation Debugger-Poachable Feature Request OmniSharp
#327 opened May 16, 2016 by chuckries
4
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.