Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarification on LocalTransport's default killOnClose value affecting GDB disposal #1397

Open
RomanGavrilov opened this issue Apr 14, 2023 · 0 comments
Open

Clarification on LocalTransport's default killOnClose value affecting GDB disposal #1397

RomanGavrilov opened this issue Apr 14, 2023 · 0 comments

Comments

@RomanGavrilov
Copy link

RomanGavrilov commented Apr 14, 2023 •
edited
Loading

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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RomanGavrilov