[Lldb-commits] [lldb] [lldb] Improved lldb-server stability for remote launching (PR #100659)

[Pavel Labath via lldb-commits]

labath wrote:

> > that could mean that something like `$CC hello.cc && ./a.out` could fail (what we're doing here isn't fundamentally different than that).
> 
> The difference is that cc creates a.out and exits itself. But `lldb-server platform` is still running after creating the executable. Something must be flushed?

Ok, this wasn't the best analogy. I still stand by my analysis of the problem though.



> See also [golang/go#22315](https://github.com/golang/go/issues/22315)

That's exactly the problem I'm describing here. And I'm considering something like https://github.com/golang/go/issues/22315#issuecomment-2188688461 as the solution (if we really do go through with this). The bug is that the FD gets leaked, and the fix is to make sure it doesn't get leaked. Waiting is a workaround because there's no guarantee that whoever we leak it to will close it.. ever. The only reason the workaround is here is because the bug was in third party code we can't change (everywhere.. we did change it, but only for new androids)

https://github.com/llvm/llvm-project/pull/100659