microsoft / microsoft/vscode-mono-debug

Docker Container Fails to Debug Past V15.8

Open
#72 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
180
Forks
182
Avg merge
1d 8h
Merged PRs (30d)
1

Description

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/

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with the Mono V5.12 container and the example debugger-agent parameters, comparing extension versions greater than 16.0 with 15.8 or less. Done means the debugger attaches, triggers breakpoints, and starts normally when suspend=y is used.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, docker
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.