-
Notifications
You must be signed in to change notification settings - Fork 173
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.
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
Unable to debug with v0.16.0 #68
Comments
Hm this sounds like it might have been caused by 0f7bfa8.
I can see how that might happen, if I remember correctly I'll probably need to revert that commit and put it behind an option. |
Should be fixed now in v0.16.2, thanks for the report! |
Wonderful, thanks for the fast turnaround on that one. I did notice that on 0.16.2, the break on exception feature seems to be no longer working (it works for me on 0.15.8). Entirely possible that I've done something wrong, just thought I'd check if it's related to the above issue. In case it helps, here is my configuration. I haven't touched it recently, so it would have been the same when testing against the two different versions of the extension.
|
I'm having the same issue with 0.16.2, VSCode does not detect hit breakpoints, but debugged application pauses upon hitting that breakpoint and does not respond unless I stop debugging. 0.16.0 Shows an error |
Hi all, just a heads up that after upgrading to v0.16.0 of this extension, I'm unable to debug my C#/mono application. Downgrading to v0.15.8 fixes the problem. Here is my launch.json:
I'm not sure if there's a log somewhere which I can upload - let me know if there's any extra info I can give. From my perspective, I normally see something in the debug console like this when I start debugging:
mono --debug --debugger-agent=transport=dt_socket,server=y,address=127.0.0.1:46391 Bin/Program.exe
. When using v0.16.0, however I just seemono Bin/Program.exe
, and the program appears to be launched without the debugger attached. The program also doesn't seem to run correctly - I haven't tested extensively but I get some errors along the lines ofdebugger-agent: Unable to listen on 3
when attempting to compile scripts viaSystem.CodeDom.Compiler.CompileAssemblyFromFile()
. I don't get these errors when running normally (e.g. without vscode or vscode-mono-debug).Apologies if I'm misusing the extension somehow - and let me know if I can provide any other diagnostics.
The text was updated successfully, but these errors were encountered: