microsoft / microsoft/MIEngine
Connection refused: OpenDebugAD7 --server --pauseForDebugger [WSL2] how to debug?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
Hello.
I'm trying to debug the OpenDebugAD7.exe following the documentation available to gather more information about this extremely annoying performance issue reported in c++ tools extension
However, the attach it's failing when running this with Dotnet extension. I also tried running a GDB with target remote to see if it's able to connect.
- Connection refused
Config:
{
"configurations": [
{
"name": ".NET Core Attach",
"type": "coreclr",
"request": "attach",
"debugServer": 4711
}
]
}
Tested with different ports with same result.
Environment:
- WSL Ubuntu 22.04
How I built:
dotnet build src/MIDebugEngine-Unix.sln
./PublishOpenDebugAD7.sh whatever
The thing case is that if I run without --pauseForDebugger, it seems that the port it's accesible and even got connection with GDB.
./OpenDebugAD7.exe --server
Shouldn't start listening at least and wating for debugger in the port? Or I have misunderstood it?
Related, if I try to attach using the coreclr + OpenDebugAD7 --server --pauseForDebugger, it crashes:
Stopping due to fatal error: FileNotFoundException: Could not find file '/home/borjamf/MIEngine/bin/Debug/vscode/coreclr.ad7Engine.json'.
Could you guide me how to be able to debug this?
Thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the WSL Ubuntu 22.04 setup using src/MIDebugEngine-Unix.sln, PublishOpenDebugAD7.sh, and the OpenDebugAD7.exe commands in the report. Compare the --server and --pauseForDebugger cases with the shown coreclr attach configuration, and inspect the reported missing coreclr.ad7Engine.json. Done means identifying why the connection or file lookup fails and documenting a working debug setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux, vscode
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100