Remove Status::WasInterrupted() that checks whether the underlying error
code matches EINTR. ProcessGDBRemote::ConnectToDebugserver() is its
only call site, and it does not seem correct there. After all, EINTR
is precisely when we want to retry, not stop retrying. Furthermore,
it should not really matter since we should be catching EINTR
immediately via llvm::sys::RetryAfterSignal() but that's another story.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
Yeah, random signals should cause a retry (they probably do already) and I think user interrupts should be handled differently (at a higher level).