- User Since
- Sep 13 2019, 1:09 PM (47 w, 2 d)
Jun 1 2020
May 28 2020
I think that Antonio's solution (with a fair amount of cleanup) would be fine. However, I'm still puzzled by the vscode behavior. I find it hard to believe that lldb is the only process which outputs random blurbs to stderr. Leaving applications which do that to hang is not very nice. If vscode does not intend to read from stderr, *it* should redirect it to /dev/null.
Super. How do I get this landed now, does someone have to commit it manually or does closing the diff take care of it?
May 27 2020
I don't think we should ignore stderr this at this level, we should either do what Pavel suggests or send the stderr back through the protocol.
May 26 2020
Sep 19 2019
That would be good, thanks
Sep 16 2019
Thanks for the review, how can I get this landed now?