`"cwd"` launch option ignored with custom launch commands or upon attach

Open

#1,494 opened on Mar 5, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 52/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Stale
Tech stack: csharp
Domain: devtools

Research direction

Read LaunchLocalDebuggerCommand() in src/MICore/UnixUtilities.cs and GetInitializeCommands() in src/MIDebugEngine/Engine.impl/DebuggedProcess.cs. Trace how the debugger working directory is selected when cwd, processId, or customLaunchSetupCommands are present. Done means cwd is applied consistently, including custom-launch and attach scenarios, with relevant behavior verified.

Written by the indexing model from the issue text.

Description

Upon startup, MIEngine sets the debugger working directory to the location of the debugged program executable (See LaunchLocalDebuggerCommand() in src/MICore/UnixUtilities.cs).

Later, if neither the "processId" or "customLaunchSetupCommands" options are set, then the debugger working directory is set to the path held in the "cwd"/WorkingDirectory launch option. If "processId" or "customLaunchSetupCommands" is set, the debugger working directory remains as that of the debugged program executable. See GetInitializeCommands() in src/MIDebugEngine/Engine.impl/DebuggedProcess.cs

I believe that the path held in "cwd" should be applied as the debugger working directory in all cases - for consistency and because documentation does not say that this option is sometimes ignored

Dominant language: C#
Stars: 859
Forks: 233
Avg merge: 1d 6h
Merged PRs (30d): 3

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.

Similar issues

[quality-improver] Repository Quality: AzureFoundry Extension Missing from Self-Registration Acceptance Test Open

type/automation type/tech-debt

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

microsoft/testfx#11431 · Opened Sep 21, 2026
[Bug]: Composite `ui screenshot` success output ignores `--quiet` Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

microsoft/winappCli#914 · Opened Sep 21, 2026
GeometryHelper.FlattenArc / FlattenCubicBezier / FlattenQuadraticBezier emit a NaN point when the segment count truncates to 0 (0/0) — a Path with a sub-pixel arc fail-fasts Windows with D2DERR_BAD_NUMBER (root cause of #8512, #13757) Open

t/bug

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

dotnet/maui#38751 · 1 reaction · Opened Sep 21, 2026
[CI Failure] Flaky: MauiBuildQueueTests.CancelQueuedResource_CompletesGracefullyAndDoesNotAcquireSemaphore asserts exact exception type but sometimes gets TaskCanceledException instead of OperationCanceledException Open

ci-failure-cause test-failure

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

microsoft/aspire#20284 · Opened Sep 21, 2026
The login flow's text-link submit is 42 px tall on a narrow screen; its docblock says 44 Open

area:auth FE mvp P3

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

klasolsson81/jobbliggaren#1788 · Opened Sep 21, 2026

More C# issues