Clarification on LocalTransport's default killOnClose value affecting GDB disposal
RomanGavrilov opened this issue · 0 comments
RomanGavrilov commented
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?