You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, I use this extension to debug a docker container running on my local machine and I noticed with the newer version >16.0 that the debugger fails to actually debug when connecting to the container.
Its weird because I can see the threads running in my program so it does "attach" to the instance of mono, but no breakpoints are triggered and the program just runs. Also, if I set my mono debug params to suspend=y it attaches (I can see the main thread appear in Call Stack) but remains suspended and never kicks off the program.
I can still use version 15.8 or less and it works perfectly.
Example mono params in container: --debug --debugger-agent=transport=dt_socket,server=y,address=0.0.0.0:55555,suspend=y
Hey, I use this extension to debug a docker container running on my local machine and I noticed with the newer version >16.0 that the debugger fails to actually debug when connecting to the container.
Its weird because I can see the threads running in my program so it does "attach" to the instance of mono, but no breakpoints are triggered and the program just runs. Also, if I set my mono debug params to suspend=y it attaches (I can see the main thread appear in Call Stack) but remains suspended and never kicks off the program.
I can still use version 15.8 or less and it works perfectly.
Example mono params in container:
--debug --debugger-agent=transport=dt_socket,server=y,address=0.0.0.0:55555,suspend=y
Mono V5.12 Running in Container:
http://download.mono-project.com/repo/ubuntu/dists/stable-xenial/snapshots/5.12.0.226/
The text was updated successfully, but these errors were encountered: