Fix to the interrupt timeout handling: reset the timeout on re-entry

[jingham]

Summary

The new timeout handling missed one case where we need to reset the computed timeout: when a packet interrupts the Continue wait, but asks to re-enter the wait loop when done.

This is the only other way to get back to the ReadPacket call, so this is the only other place that requires reset.

[jingham]

It's less error-prone if we just reset the timeout to the default when we wake up from ReadPacket. This isn't an expensive operation...

lldb/source/Plugins/Process/gdb-remote/GDBRemoteClientBase.cpp

StateType GDBRemoteClientBase::SendContinuePacketAndWaitForResponse(
   // check that the connection hasn't dropped.  When we wake up we also check
   // whether there is an interrupt request that has reached its endpoint.
   // If we want a shorter interrupt timeout that kWakeupInterval, we need to 
   // choose the shorter interval for the wake up as well.
   std::chrono::seconds computed_timeout = std::min(interrupt_timeout, 
                                                    kWakeupInterval);
   for (;;) {
     PacketResult read_result = ReadPacket(response, computed_timeout, false);
+    // Reset the computed_timeout to the default value in case we are going
+    // round again.
+    computed_timeout = std::min(interrupt_timeout, kWakeupInterval);
     switch (read_result) {
     case PacketResult::ErrorReplyTimeout: {
       std::lock_guard<std::mutex> lock(m_mutex);
       if (m_async_count == 0) {
         continue;
       }
       auto cur_time = steady_clock::now();
       if (cur_time >= m_interrupt_endpoint)