microsoft / microsoft/MIEngine
Clarification on LocalTransport's default killOnClose value affecting GDB disposal
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
I'm not certain if my question makes complete sense, so I'd appreciate any clarification.
It seems that when using LocalTransport the killOnClose flag is consistently set to false due to the parent constructor's default value. As a result, the GDB is not being properly disposed. Can you please help me understand if my observation is accurate? If so, would either setting the killOnClose flag to true in LocalTransport or moving this flag to launch options and passing it to the LocalTransport constructor be potential solutions?
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 tracing LocalTransport's constructor to the parent constructor and inspect how the killOnClose default is applied. Then follow the GDB disposal path and the launch options mentioned in the issue. Done means confirming whether the observed behavior is a bug and reaching a maintainer-approved resolution for the flag's ownership and default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100